[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AW: [equinox-dev] OSGi Logger Service <-> Eclipse Plugin Logger
- From: "Stuart McCulloch" <stuart.mcculloch@xxxxxxxxxx>
- Date: Thu, 11 Oct 2007 11:51:49 +0800
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=GlIO7/BhQAadpLW8NrWpJYWsTM1zg4toICiqJV46Cewt+qZaYDfmaqosQT7A6E4yJ6r0WP7JzcQYtKQYlTA0Dv7RDD/pQ5w/Ct0qa+qABgm+9pUqWIifz4glZh+C0FHLnowLuyvB9oFLtMvm/AKAOk+aCNvMUDPdOq20j1Qf9QA=
On 09/10/2007, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
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.tracker packages).
It uses the OSGi service registry, rather than the Eclipse extension registry.
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;
Jakarta Commons Logging
Avalon Logging API
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,
equinox-dev mailing list