Some form of namespace is generally needed to locate the model, i.e.,
the EPackage. Is your model XML Schema based? We do support schemas
with no target namespace, but it's more complex to handle that and to
set it up properly. You could look at what's generated for an XML
schema that doesn't have a target namespace. In particular there's an
extended meta data annotation on the EPackage and the generated resource
factory's createResource method sets options to ensure that this
annotation is respected and to ensure that the EPackage can still be
On 29/01/2013 7:05 AM, Jae Lee wrote:
> First, thank you to Ed Merks who solved my problem last time.
> So, with the model file you can generated an xml file and by somehow,
> the generated xml file has the namespace in front of every element.
> For example:
> <caparch:archTypes> while I want to have <archTypes>.
> how should I disallow the editor to attach caparch: in front of every
> element? Thank you.