|
Re: .ecore model naming conventions? [message #381189 is a reply to message #381188] |
Fri, 10 August 2007 11:17 |
Ed Merks Messages: 33139 Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------040108020506080007070009
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Bernie,
Please use the EMF newsgroup for EMF questions; I've added it to the
"to" list of the reply.
You can change the name of the .ecore file on the last page of the
wizard by clicking on the file name and changing it. All other
properties you can change either with annotations in the schema
XML Schema to Ecore Mapping
< http://www.eclipse.org/modeling/emf/docs/overviews/XMLSchema ToEcoreMapping.pdf>
or via properties in the .genmodel; all genmodel properties are
preserved when you "Reload..." the model the next time.
Bernie wrote:
> 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?
--------------040108020506080007070009
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Bernie,<br>
<br>
Please use the EMF newsgroup for EMF questions; I've added it to the
"to" list of the reply.<br>
<br>
You can change the name of the .ecore file on the last page of the
wizard by clicking on the file name and changing it. All other
properties you can change either with annotations in the schema<br>
<blockquote><a
href=" http://www.eclipse.org/modeling/emf/docs/overviews/XMLSchema ToEcoreMapping.pdf">XML
Schema to Ecore Mapping</a><br>
</blockquote>
or via properties in the .genmodel; all genmodel properties are
preserved when you "Reload..." the model the next time.<br>
<br>
<br>
Bernie wrote:
<blockquote cite="mid:f9hf7i$njq$1@build.eclipse.org" type="cite">I
have two .xsd files.
<br>
First.xsd has no includes and defines two elements and some
simple&complex types.
<br>
Second.xsd includes First.xsd and defines more elements and
simple&complex types.
<br>
<br>
When creating a EMF project from Second.xsd
<br>
- the name of the .ecore file and root object name is based on
First.xsd (the included file).
<br>
- after deleting just the elements from First.xsd the .ecore file and
root object name is based on Second.xsd.
<br>
<br>
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.
<br>
<br>
The question:
<br>
Is there a way to override this default behavior so Second.xsd is used
as the .ecore file and root object name? <br>
</blockquote>
<br>
</body>
</html>
--------------040108020506080007070009--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Re: .ecore model naming conventions? [message #599255 is a reply to message #381188] |
Fri, 10 August 2007 11:17 |
Ed Merks Messages: 33139 Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------040108020506080007070009
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Bernie,
Please use the EMF newsgroup for EMF questions; I've added it to the
"to" list of the reply.
You can change the name of the .ecore file on the last page of the
wizard by clicking on the file name and changing it. All other
properties you can change either with annotations in the schema
XML Schema to Ecore Mapping
< http://www.eclipse.org/modeling/emf/docs/overviews/XMLSchema ToEcoreMapping.pdf>
or via properties in the .genmodel; all genmodel properties are
preserved when you "Reload..." the model the next time.
Bernie wrote:
> 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?
--------------040108020506080007070009
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Bernie,<br>
<br>
Please use the EMF newsgroup for EMF questions; I've added it to the
"to" list of the reply.<br>
<br>
You can change the name of the .ecore file on the last page of the
wizard by clicking on the file name and changing it. All other
properties you can change either with annotations in the schema<br>
<blockquote><a
href=" http://www.eclipse.org/modeling/emf/docs/overviews/XMLSchema ToEcoreMapping.pdf">XML
Schema to Ecore Mapping</a><br>
</blockquote>
or via properties in the .genmodel; all genmodel properties are
preserved when you "Reload..." the model the next time.<br>
<br>
<br>
Bernie wrote:
<blockquote cite="mid:f9hf7i$njq$1@build.eclipse.org" type="cite">I
have two .xsd files.
<br>
First.xsd has no includes and defines two elements and some
simple&complex types.
<br>
Second.xsd includes First.xsd and defines more elements and
simple&complex types.
<br>
<br>
When creating a EMF project from Second.xsd
<br>
- the name of the .ecore file and root object name is based on
First.xsd (the included file).
<br>
- after deleting just the elements from First.xsd the .ecore file and
root object name is based on Second.xsd.
<br>
<br>
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.
<br>
<br>
The question:
<br>
Is there a way to override this default behavior so Second.xsd is used
as the .ecore file and root object name? <br>
</blockquote>
<br>
</body>
</html>
--------------040108020506080007070009--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.15712 seconds