|
Re: emf model importer: prefix names are always "type" [message #70366 is a reply to message #70325] |
Sat, 03 February 2007 12:34 |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Brian,
You can use the ecore:nsPrefix annotation as described in
http://www.eclipse.org/modeling/emf/docs/overviews/XMLSchema ToEcoreMapping.pdf
to control this.
Brian Vetter wrote:
> When I use the emf model importer to pull in an XSD into an ecore
> model, the name prefix placed in the ecore model for all of the
> referenced/imported types are the same: "types". While it doesn't seem
> to bother the emf internals too much, it causes much grief when I use
> Teneo to map these types to database tables. The prefix names are used
> to scope the table names.
>
> I think the proper behavior would be to use the prefix names as
> defined in the XSDs (either the including XSDs or perhaps the ones
> where the types are actually created). Is this a reasonable request or
> is there something that keeps this from working this way?
>
> I can work around this temporarily by doing this by hand for now, but
> ultimately, I need to do this completely programmatically.
> Brian
|
|
|
Re: emf model importer: prefix names are always "type" [message #602115 is a reply to message #70325] |
Sat, 03 February 2007 12:34 |
Ed Merks Messages: 33139 Registered: July 2009 |
Senior Member |
|
|
Brian,
You can use the ecore:nsPrefix annotation as described in
http://www.eclipse.org/modeling/emf/docs/overviews/XMLSchema ToEcoreMapping.pdf
to control this.
Brian Vetter wrote:
> When I use the emf model importer to pull in an XSD into an ecore
> model, the name prefix placed in the ecore model for all of the
> referenced/imported types are the same: "types". While it doesn't seem
> to bother the emf internals too much, it causes much grief when I use
> Teneo to map these types to database tables. The prefix names are used
> to scope the table names.
>
> I think the proper behavior would be to use the prefix names as
> defined in the XSDs (either the including XSDs or perhaps the ones
> where the types are actually created). Is this a reasonable request or
> is there something that keeps this from working this way?
>
> I can work around this temporarily by doing this by hand for now, but
> ultimately, I need to do this completely programmatically.
> Brian
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.02935 seconds