| .ecore model naming conventions? [message #599240] |
Fri, 10 August 2007 10:37 |
 Bernie Bussiere
Messages: 13
Registered: July 2009 |
Junior Member |
|
|
I have two .xsd files.
First.xsd has no includes and defines two elements and some simple&complex
types.
Second.xsd includes First.xsd and defines more elements and simple&complex
types.
When creating a EMF project from Second.xsd
- the name of the .ecore file and root object name is based on First.xsd
(the included file).
- after deleting just the elements from First.xsd the .ecore file and root
object name is based on Second.xsd.
My expectations were that the .ecore file and root object name would always
be based on Second.xsd, the file being passed into the EMF project creation
wizard. It appears to be choosing the first file that it finds an element
in.
The question:
Is there a way to override this default behavior so Second.xsd is used as
the .ecore file and root object name?
|
|
|
Powered by
FUDForum. Page generated in 0.02624 seconds
] 
Search
Help
Register
Login
Home
