Bug 533544 - [runtime] Save with a useable schemaLocation
Summary: [runtime] Save with a useable schemaLocation
Status: NEW
Alias: None
Product: QVTd
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-13 07:57 EDT by Ed Willink CLA
Modified: 2018-07-13 06:59 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2018-04-13 07:57:53 EDT 
Currently both XMLResource.OPTION_SCHEMA_LOCATION and XMLResource.OPTION_SCHEMA_LOCATION_IMPLEMENTATION are set true which is good if the referenced models are Java code in plugins. But not so good for viewing outputs of CGed TXes whose Java was created on the fly.

If only XMLResource.OPTION_SCHEMA_LOCATION is set, we might hope that dynamic *.ecore is used, but seemingly since we ran with Java the schemaLocation tries to be Java.

See if EMF can be persuaded to save a *.ecore schemaLocation for Java models. ?? change the Resource.uri when saving ??
Comment 1 Ed Willink CLA 2018-07-13 06:59:09 EDT 
Perhaps another aspect of the same problem.

If the .settings/org.eclipse.m2m.qvt.oml.mmodel.urimap is used to define a nsURI location, that location needs to be present as a schemaLocation to ensure that the generated file can be loaded by the Sample Ecore Model Editor.