springsource-dm-server-2.0.0.RELEASE and Terracotta-3.2.0-ee

[vishalj]

We tried out a sample bundle deployment on springsource-dm-server-2.0.0.RELEASE and Terracotta-3.2.0-ee.



A shared object (com.pg.dm.MyObject) was loaded from boot classpath.



A bundle(ServiceBundle) instantiating a bean (com.pg.services.MyService) was instantiating the shared object (MyObject) in its init method,

and exposing the proper method to update and get the properties for the shared object .



The deployement of ServiceBundle was successful on springsource-dm-server-1.0.2.RELEASE but the same failed on springsource-dm-server-2.0.0.RELEASE

The Exception on deployment looks like

java.lang.IllegalStateException: This classloader instance has not been registered (loader class:org.eclipse.osgi.launch.EquinoxFWClassLoader).

Are there some classloader changes at equinox level .

Regards,
Vishal

[njain15]

We figure this @Terracotta. The issue is with the naming of the EquinoxFWClassLoader. Ideally shared object classes should be packaged in bundles instead of making them available via system classpath. If done that way, it should just work fine on DM server 2.