|[TEXO] Allowed chars in EPackage name [message #684302]
||Wed, 15 June 2011 11:43
Registered: June 2011
which are the allowed chars in the name feature of a EPackage?
We used to have names woth dot-separated elements ("org.test.mytest"); this worked until about 1 month ago, but now Texo rejects it with "The name 'org.test.mytest' is not well formed".
Was this changed each EPackage should really model only one component in a fully qualified Java package name (that is, to support nesting EPackages)?
[Updated on: Wed, 15 June 2011 11:43]
Report message to a moderator
|Re: [TEXO] Allowed chars in EPackage name [message #719308 is a reply to message #719123]
||Fri, 26 August 2011 16:15
| Ed Merks
Registered: July 2009
The package name isn't allowed to contain dots, but the XSDEcoreBuilder
passed the data base to the importer in that form, which then strips it
out so it can set the GenPackage.basePackage from that. With the work
on Xcore I'm looking at better ways to capture this information, i.e.,
an annotation with the GenModel's nsURI as the source and a basePackage
key. Given that approach, it will be better for the XSDEcoreBuilder to
use that approach as well (though I suppose changing the builder could
break existing clients, so I'm not sure how best to address that concern
On 25/08/2011 11:53 PM, Martin Taal wrote:
> Hmm I have not thought about that, I will ask Ed what the EMF approach
> is here.
> gr. Martin
> On 08/26/2011 08:51 AM, gdelprete wrote:
>> I've seen the bug was closed as invalid and it was decided not to
>> allow dots in the EPackage name. This is fine for me.
>> Please note, however, that it you create an Ecore model from an XSD
>> file, the package name will be generated as a fully
>> qualified name with dots. It's probably better now to change the
>> algorithm for EPackage name generation for the
>> XSD->Ecore case so that it it is consistent to what Texo expects when
>> generating che code.
Powered by FUDForum
. Page generated in 0.02641 seconds