Hi Filippo, I'm aware of that, but suppose you have the following situation (based on the fact stated by Borja that there are two bundles exporting the same package):
Bundle A: Export-Package: org.foo (contains class Wibble, used by org.bar.Wobble) Import-Package: org.foo Bundle B: Export-Package org.foo (does NOT contain class Wibble) Import-Package: org.foo If A is installed and resolved first, then the class org.foo.Wibble will be accessible to org.bar.Wobble because the framework will choose to export package org.foo from A rather than import it. If B is installed and resolved first, then the framework will export org.foo from B and import it into A, so the class org.bar.Wobble will not be able to access org.foo.Wibble. It is incorrect to construct bundles this way, but it may explain why Borja received an error using FileInstall but not when manually installing in a certain order. Regards Neil On Tue, Jun 30, 2009 at 1:27 PM, Filippo Diotalevi<[email protected]> wrote: > On Tue, Jun 30, 2009 at 2:16 PM, Neil Bartlett<[email protected]> wrote: >> This may be due to the order in which you installed the bundles. If >> you have got errors in your metadata then the problem might not appear >> if you always install your bundles in the same order, but installation >> order with FileInstall is not controllable (nor should it be). > > In FI all the discovered bundles are installed first, and then started. > > So when a bundle starts, all the exported packages from all the > discovered bundles are already available. > > -- > Filippo Diotalevi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
