|
|
|
Re: Global EMF Registry [message #664204 is a reply to message #664179] |
Thu, 07 April 2011 19:48 |
Ed Merks Messages: 33218 Registered: July 2009 |
Senior Member |
|
|
Enrico,
Comments below.
Enrico Biermann wrote:
> Hello Ed,
>
> thanks for your response. I don't use generated code in this case and
> therefore don't have this package in the global registry (except when
> I register it manually). My problem is that in one case (file) the
> EClasses from the demandRegistry is used to create EObjects
That would happen only if you've not registered the package in the
global package registry or the package registry in the resource set
you're using the load the instance.
> and in the other case (proxy) the global registry is used.
Proxies are just created EObjects, so I'm not sure I understand which
case is which.
> For both cases an EPackage is created if it did not already exist in
> the specific registry.
Depending on the option that might well be the case.
>
> I don't want to use the content handler or its registry (it is
> protected anyway), but EMF is using it when loading such an xmi-file.
I don't understand how what the content handler does affects the loading
of your instances.
> Is there any way to provide the *real* EPackage when opening such
> files or change the content handlers strategy to find a valid EPackage
> ("don't look in the metadata registries but use the global one")?
You can register your packages in the resource set's package registry.
>
> Regards,
> Enrico
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03225 seconds