2009/3/6 Stevens Gestin <[email protected]> > Hi, > > without an hint on your error it's a bit difficult to help. >
yes, seeing the actual error or exception trace would be useful as well as your settings for system packages / bootdelegation also note that while OSGi attempts to isolate bundles, because it runs on top of the JVM it is still possible for code to get access to other classloaders by techniques such as reflection, or simply by calling getClassLoader() on a passed in type or instance. complete isolation is only possible with low-level runtime support Stevens > > On Fri, Mar 6, 2009 at 7:07 AM, Pete Haidinyak <[email protected]> wrote: > > > I am embedding Felix in an application I am porting and was playing > around > > with logging with Log4j. I wanted both the application and Felix to use > > Log4j. I put the Log4j jar in the classpath and loaded a Log4j bundle. I > was > > getting an error doing this. > > My question is I thought OSGi isolated the bundles from each other and > the > > classpath unless you tell it other wise. Why would having log4j on the > > classpath cause a bundle to have problems? > > > > THanks > > > > -Pete > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > -- > Le respect commence par celui de l'environnement > -- Cheers, Stuart
