Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 319434

Summary: Inconsitent XMI - Schema generation for Ecore models
Product: [Modeling] EMF Reporter: Heiko Ahlig <nacor>
Component: XML/XMIAssignee: Ed Merks <Ed.Merks>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Heiko Ahlig CLA 2010-07-09 17:13:27 EDT 
Build Identifier: I20100608-0911

The generation of XMI schemas is inconsistence for the names and schemalocation inside the schemas.

The bottom steps produce the following errors/inconsistencies
1. The name of the schema files for each package gets the suffix XMI but inside the schmea it references to a file without the suffix.
2. It generates an XMI.xsd schema file inside the project-model-folder, but references inside the schema to platform:/plugin/org.eclipse.emf.ecore/model/XMI.xsd

Maybe additional problems
I think many people will use the schemas outisde the model or eclipse framework. So I seems that problematical to use references wit a "platform"-URL

An other problem are references between xmi schemas between diffrent model projects, every model generates the XMI schema instead use the xmi file from the depending schema.


Reproducible: Always

Steps to Reproduce:
1. Build an ecore model with  package and a subpackage an classes where one referenced or subclass  the class of the other package.
2. Set Generate Schema inside genmodel on true
3. Set ResourceType for the packages to XMI
4. Generate model code (wich includes schema generation)
Comment 1 Ed Merks CLA 2010-07-10 11:36:52 EDT 
XMI Schema generation was completely redesigned and is now invoked by exporting your model to an XML or XMI schema rather than as a side effect of generation; the older stuff was left in place but, as you've noticed, it doesn't work well at all.  As a side note, an XMI schema is, in my opinion, a completely useless artifact.  I know of no situation where it's actually been useful even in some minimal way.
Comment 2 Ed Merks CLA 2010-07-10 11:37:56 EDT 
We won't fix/update the older design because there's not enough information available to produce proper cross file references.