Bug 540691 - No schemaLocation saved when dynamic metamodel inherits from non-dynamic
Summary: No schemaLocation saved when dynamic metamodel inherits from non-dynamic
Status: NEW
Alias: None
Product: QVTo
Classification: Modeling
Component: Engine (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 10
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-01 09:39 EDT by Christopher Gerking CLA
Modified: 2018-11-01 09:39 EDT (History)
0 users

See Also:

Attachments
Repro QVTo project (2.56 KB, application/x-zip-compressed)
2018-11-01 09:39 EDT, Christopher Gerking CLA 		no flags Details
View All 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 Christopher Gerking CLA 2018-11-01 09:39:14 EDT 
Created attachment 276445 [details]
Repro QVTo project

The attachment includes a repro that makes QVTo fail to include a schemaLocation in a dynamic output model. The reason is that the corresponding metamodel uses a non-dynamic type like http://www.eclipse.org/emf/2002/Ecore#//EObject as a supertype for one of its classes. Therefore the corresponding instances are actually of class EObject at the Java level. On save, EmfUtil.isDynamic(...) therefore fails to detect that they are still dynamic instances that require a schemaLocation.