Eclipse Community Forums: EMF » [CDO] "Not a top level package" exception

Help

Home

Home » Modeling » EMF » [CDO] "Not a top level package" exception

Show: Today's Messages :: Show Polls :: Message Navigator

[CDO] "Not a top level package" exception [message #423516]

Wed, 01 October 2008 16:55

Tom Crockett

Messages: 54
Registered: July 2009

Member

When I use the DemandPopulating package registry, it has a problem with
the fact that I have a model which is in a subpackage of another model.
CDOPackageRegistry.putEPackage() throws an illegal argument exception. Why
is this not supported?

Report message to a moderator

Re: [CDO] "Not a top level package" exception [message #423522 is a reply to message #423516]

Wed, 01 October 2008 18:44

Eike Stepper

Messages: 6468
Registered: July 2009

Senior Member

Tom Crockett schrieb:
> When I use the DemandPopulating package registry, it has a problem
> with the fact that I have a model which is in a subpackage of another
> model. CDOPackageRegistry.putEPackage() throws an illegal argument
> exception. Why is this not supported?
It's mainly not supported because the serialization of a subpackage is
bound to (i.e. contained in) the serialization of the containing package.

Cheers
/Eike

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator

Re: [CDO] "Not a top level package" exception [message #423529 is a reply to message #423522]

Wed, 01 October 2008 19:29

Tom Crockett

Messages: 54
Registered: July 2009

Member

Eike Stepper wrote:

> Tom Crockett schrieb:
>> When I use the DemandPopulating package registry, it has a problem
>> with the fact that I have a model which is in a subpackage of another
>> model. CDOPackageRegistry.putEPackage() throws an illegal argument
>> exception. Why is this not supported?
> It's mainly not supported because the serialization of a subpackage is
> bound to (i.e. contained in) the serialization of the containing package.

In that case I think there may be a bug with the lazy loading package
registry, because it's attempting to register these subpackages and then
this exception gets thrown.

Report message to a moderator