On Saturday 15 December 2007 02:17, Abdelgadir Ibrahim wrote: > Any idea why this behaviour??. I suspect it is a class loader issue because > the two bundles will have different class loaders. Note that I am using > jdk1.5 and have enabled the new feature of dynamic proxy generation to > avoid the need to run the rmic tool.
I can't figure out why it wouldn't work, but is related to that the RMI subsystem will create a child classloader using the "receiving bundle"'s classloader as the parent. Somehow, a classloader is needed and something goes wrong. I am somewhat confident that if you use JDK1.2 style RemoteStub, you won't have this problem, since the MyService_Stub class will be declared explicitly in OSGi. The extra rmic step ain't that much of trouble, since you only need to run it when the Remote interface has changed its signature (=seldom). HTH Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
