Thank you. Now it's working.
2007/7/30, Logan Barron <[EMAIL PROTECTED]>: > > Hello Jaime, > > Package the bundle with the dependencies and declare them in your bundle's > classpath. > > If log4j.jar is in your bundle's lib folder, your manifest.mf would > include > an entry similar to this: > > *Bundle-ClassPath: .,/lib/log4j.jar* > > Look at your R4 spec. Study DynamicImport-Package, Import-Package, and > Export-Package... > > Regards, > > -Barron > > > > On 7/30/07, Jaime Osgi <[EMAIL PROTECTED]> wrote: > > > > If my OSGi bundle depends on a .JAR file, that it's not currently an > OSGi > > bundle, how could I make it work?. > > > > For example, if my OSGi bundle has some dependencies to Log4J library > (or > > other library), it will raise ClassNotFound exceptions due for any > > invocation to Log4J classes. How can I solve it?. Perhaps, creating an > > OSGi > > bundle with the classes included in the Log4J .JAR file?. Is there any > > other > > method?. > > > > Thanks, > > Jaime > > > > > > -- > Cell: 678.656.5924 > Your Friend, > Barron Logan >
