On Monday 31 March 2008 23:02, Richard Martin wrote: > I had first though pax-logging-client would be like a > wrapped version of the logger classes that did service discovery and > passed the calls to all registered services. But now I'm guessing it's > not, if I wanted the non bundle code to use pax-logging would I need > to write something like this?
Not sure what you are saying... Do you want non-OSGi code to use the Pax Logging Service?? If so, you need to fabricate some stuff yourself, namely; If you are using Felix, you can create so called Framework Extensions, which are essentially your code implementing the BundleActivator API (start() and stop()) from which you can obtain the OSGi services. So, you will need to create a Framework Extension that tracks the Pax Logging Service similar to how the legacy APIs does it. You will probably have some class namespace issues, as I thikn the Pax Logging Service API will need to be in the framework classloader and not in the Pax Logging API bundle as it is now. It might be possible to modify the Pax Logging API to become Felix Framework Extension compatible. Have not looked into it. More help if you get going. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
