On 12/10/2007, Scott Lewis <[EMAIL PROTECTED]> wrote: > > Hi Stuart, > > Thanks...this is great. Just for my and others info, how much code is > pax? >
well 'pax' is an umbrella project that covers all things OSGi at www.ops4j.org ( ie. logging and http services, provisioning with pax-runner, building projects with pax-construct, dynamic modular wicket with pax-wicket, etc, etc... ) the 'pax-logging-api bundle' is not trivial, but it is really just the logging APIs for log4j, commons, slf4j, avalon, knopflerfish, osgi and it's own API - plus a couple of factory classes the API bundle in total is around 57k, but it can replace any major logging API jar that you might already have on your classpath, so you may find you save space. For the time being my trivial class is just 2500 bytes, so as 'last ditch' ( > i.e. if pax or no others are available) it works OK but having something > like pax as part of equinox impl would be nice. > FYI, it also works well with other OSGi frameworks, such as Knopflerfish and Felix. Scott > > Stuart McCulloch wrote: > > On 09/10/2007, Scott Lewis <[EMAIL PROTECTED]> wrote: > > > > Thanks Niclas. > > > > I'm really looking for something much more trivial than Pax logging > > :)...so for the time being I implemented LogService myself. > > > > But thanks for the info, I may very well use Pax logging in the future. > > > > One question: what does the Pax logging API bundle depend upon? (i.e. > > extension registry?, others?). > > > > The Pax-Logging API bundle only has dependencies on the execution > environment (ie. it needs > the javax.xml.parsers and org.w3c.dom packages) and on the OSGi framework > itself (only the > org.osgi.framework, org.osgi.service.event and org.osgi.util.trackerpackages). > > It uses the OSGi service registry, rather than the Eclipse extension > registry. > > HTH > > Scott > > > > > > Niclas Hedhman wrote: > > > > On Tuesday 09 October 2007 04:28, Scott Lewis wrote: > > > > Is there any existing LogService implementation that just prints to > > System.out/System.err...that is in a bundle present for *all* Equinox > > impls (not just Eclipse)? > > > > Equinox in its purest form has no bundles in it besides the system bundle, > > and > > IIRC the internal Equinox logger is not exposed. > > > > That is, is there some basic LogService that can be used as a last-ditch > > logging mechanism (if no other LogService is available)? > > > > Pax Logging attempts to provide both OSGi Log Service functionality as > > well as > > bridging of third-party legacy APIs such as; > > > > JDK Logging > > Log4J > > Jakarta Commons Logging > > Avalon Logging API > > SLF4J > > > > KnopflerFish Log > > > > Pax Logging consists of 2 bundles. The API bundle must always be present and > > is what all the legacy code will 'bind' into when they lookup a logger the > > respective way. The Service bundle can come and go to allow for upgrade of > > > > the Log4J driven bakend, without taking down the entire application. > > When the Service is not available, the API will revert to System.out (a > > buffering version is under construction). > > > > You find Pax Logging at OPS4J, > > http://wiki.ops4j.org > > > > > > Cheers > > > > > > > > > > _______________________________________________ > > equinox-dev mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > > > > -- > Cheers, Stuart > > ------------------------------ > > _______________________________________________ > equinox-dev mailing list > [EMAIL PROTECTED]://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > _______________________________________________ > equinox-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > -- Cheers, Stuart
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
