Welcome Daniel! Not sure what "exactly" is in your API packages (like anything implementation specific that would complicate the following), but you should try to extract all these packages to a single bundle that is used by all your satellite bundles as well as the the main bundle. As a result these API's get only loaded by one single classloader and you won't ran into your current problems (the main bundle class loader could only handle the same type coming from one class loader. There is no type cast taking the class loader into account, which would be necessary in your scenario).
Cheers, Mirko btw.: your framework should tell you why the other bundles are not resolved! On Thu, Jun 4, 2009 at 4:56 PM, Daniel Dumitrescu <[email protected]> wrote: > Hi guys > > I'm really new on this mailing list, so I say hello to all. > > I'm facing a problem that may seems pretty simple. but in the last couple of > weeks it driven me crazy: > > I want to have a plugin working with different implementations of javax.jms > package (all the libs and stuff) from different providers, like JBoss, > ActiveMQ and so on, and also I want to separate these different > implementations in different OSGi bundles, that may be used by my plugin. > > This package, javax.jms. and another one, like another one, > my.package.myinterface are exported by the satellite bundles (the ones with > different JMS imlpementations) and imported into this main plugin that works > with them. > > The weird thing is that when i try to start this main plugin only one of the > satellite plugins is spawned (installed & started), and i need all the > plugins to start up. Also, it seems that the class path somehow mixes up, > although it seems that every plugin has its own classloader. > > In my main plugin i don;t have anything like "require-bundle" things, just > import javax.jms and my.package.myinterface. > > Did i do something wrong, or the OSGi specifications are this way? > > Can anyone help me? > > Thanx & regards, > Daniel > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
