Dynamic imports are pretty much as optional imports with a difference that a wire will be created (if possible) on demand after the the bundle was resolved. And once AN exported package was found the class loader of that package will be used on subsequent requests.
In my view, as stated in the specs the only way to have a split package = resources can come from different sources of the same package is to have Require-Bundle. But I guess this is way different of what you need as, I guess that, you want something like custom jsf components installed as bundles to be found by the jsf implementation, so you cannot know upfront the symbolic name of the custom jsf component. Maybe a solution to this problem, once Felix will have the fragments sorted out, is to have the jsf components as fragment bundles attached to the jsf implementation bundle. Alin On Wed, Mar 19, 2008 at 5:02 PM, Guillaume Sauthier <[EMAIL PROTECTED]> wrote: > Alin Dreghiciu wrote: > > I "especially" requested that from Peter K a while ago. Mainly my > > request was related to not export META-INF if you used * in > > Export-Package instruction, if I recall it correctly. The reasoning > > was related to how are you going to use such a package if there is > > more then one bundle that exports it as it has no name space related > > to it. To what exporter will your importing bundle get wired? More, > > your bundle that imports the META-INF will only be wired to one > > exporter as split packages are only possible with Require-Bundle. > > > Hmm, is this still true when using Dynamic imports ? > > --G > > > > Alin > > > > On Wed, Mar 19, 2008 at 1:46 AM, Guillaume Sauthier > > <[EMAIL PROTECTED]> wrote: > > > >> Hi all > >> > >> I've an issue with Bnd (in maven-bundle-plugin): I want to export the > >> META-INF "package", because some files that are inside are searched by > >> external applications (not to name them : JSF impl) and, even when I > >> explicitely put Export-Package META-INF in my .bnd file, they never show > >> up in my resulting Manifest. > >> > >> I'm not 100% sure about that, but I never read that exporting that > >> special entry was forbidden in OSGi. This is a best practice that is > >> enforced by Bnd when building the bundle Manifest :) > >> > >> Does someone has a trick to export the META-INF ? Or maybe that's > >> forbidden ? > >> > >> Cheers > >> --Guillaume > >> > >> > > > > > > > >
