felix-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Spycher <...@spycher.info>
Subject Re: Urgent - PAX -logging Vs Logback
Date Thu, 08 Dec 2011 06:38:39 GMT
Hi Matt

You may want to check this thread on the karaf list:


The gist of which is that opinions differ on pros and cons between pax
logging (with default backend log4j) and logback. Pax is more osgi-aware
and logback is simply the next generation of pax's backend log4j (same
developers) .

So yes a pax implementation with logback would be great. The problem with
that seems mainly to lie with configadmin and configuration of log4j via a
properties file vs. configuration of logback via XML: in configadmin you
would be forced to set an entire logback XML config over one property,
whilst currently you can configure log4j settings individually.



Sent from my phone
On Dec 7, 2011 9:47 PM, "Toni Menzel" <toni@okidokiteam.com> wrote:

> For starters, LogBack is a Logging implementation, right ?
> Pax Logging is a capture-all logging service for all major interfaces and
> does provide a minimalistic implementation. But you want to use Pax Logging
> + Logback in an OSGi scenario. Thats at least what i know of Logback.
> Most of that knowledge i pull from times where log4j was hot. So i might be
> wrong if log back might actually replace pax logging in some ways. That i
> don't know.
> @Matt, you are sure cross posting this on felix, aries and ops4j ?
> cheers, Toni
> On Wed, Dec 7, 2011 at 8:41 PM, Matt Madhavan <mattmadhavan@gmail.com
> >wrote:
> > Hello,
> > I would like to know the Pros and cons of PaxLogging vs Logback. I have
> > used PaxLogging a lot but the my client's Enterprise team (different
> team)
> > that sets directions, would like to use Logback.
> >
> > Can someone let me know what are the pros and cons between the two and
> > especially in the OSGi world?
> >
> > Thanks in advance!
> >
> > Matt
> >
> --
> Toni Menzel Source <http://tonimenzel.com>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message