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).
Regards, Neil On Tue, Jun 30, 2009 at 12:08 PM, Borja Miñano<[email protected]> wrote: > Hi Filippo, > > Thank you for the interest. > I've been doing some tests and i found the error. > > I used external libraries that i bundlelized with the eclipse plugin and > 2 of these libraries exported the same package with the same class. > I quit the export from one of these bundles and worked. > > But i still don't know why worked if i install it manually and don't if > file install is the installer. > > Thank you anyway. > > El mar, 30-06-2009 a las 11:12 +0200, Filippo Diotalevi escribió: >> On Mon, Jun 29, 2009 at 3:33 PM, Borja Miñano<[email protected]> wrote: >> > Hi, >> > I have a problem using file install deploying some bundles. >> > I have a bundle A that imports the package "org.xmldb.api.base", and a >> > bundle B that exports the same package. >> > The file install installs the both bundles correctly, but when it tries >> > to start bundle A a class not found exception for a class inside the >> > package. >> > >> > It is very strange because if i install the bundles manually the bundle >> > A works perfectly. But i need to make the deploy automatically with file >> > install or something similar. >> >> Hi, >> unfortunately the details you're providing aren't enough to give you >> an answer. >> >> FileInstall just calls the usual BundleContext and Bundle methods to >> install, start, stop and uninstall bundles; so, implementation-wise, >> it's absolutely equivalent to the shell. >> >> I suggest you to check your setup, and try to reproduce the error with >> the minimal set of bundles possible. >> If the problem persist, please post here the list of bundles >> installed, with import and exports, and the exception you get. >> > > > --------------------------------------------------------------------- > 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]
