Why would you so? Pax-logging has been in used for a few years now and it's working great. I still fail to understand what is besides not using paxlogging correctly.
On Sunday, April 24, 2011, Andrei Pozolotin <[email protected]> wrote: > > > > > > > > > Bartek: > > Got it; > > I guess I have to write my own osgi logging service based on slf4j and > logback :-) > > Thank you, > > > Andrei > > > -------- Original Message -------- > Subject: Re: bundles fail to start --- > http://wiki.ops4j.org/display/paxlogging/2011/02/23/Pax+Logging+1.6.1+released > From: Bartosz Kowalewski > <[email protected]> <[email protected]> > To: General OPS4J <[email protected]> <[email protected]> > Date: Sun 24 Apr 2011 07:43:37 AM CDT > > Hi Andrei, > > I guess you already found a solution for the issue you're observing. > Anyway, once you start using Pax Logging in an OSGi container, you > should abandon using the original libraries from the logging framework > of your choice in this container. Of course these original libraries > might be OSGi compliant. However, Pax Logging API priovides the same > (or similiar :) ) set of packages/classes as the chosen logging > framework and the version of these exported packages is also often the > same. Pax Logging does not export impl classes for given logging APIs. > This might cause logging frameworks to malfunction. > > ... so you should use either: Pax Logging API + PAX Logging Service or > SLF4J API and a chosen SLF4J impl. > > If you choose to use Pax Logging in the OSGi container instead of real > SLF4J and you need to execute unit tests (tests run outside of the > OSGi container), you will probably use real org.slf4j/slf4j-api and > one of the slf4j impls and not Pax Logging in these tests. > > Oh, to reset your password go to http://sso.ops4j.org. > > Best regards, > Bartek > > 2011/4/24 Andrei Pozolotin <[email protected]>: > > > you mean in "org.slf4j.impl"? - I use none; > > but slf4j-api expects to find it: > (bundles both from http://www.slf4j.org/download.html & > http://ebr.springsource.com/repository/app/bundle/version/detail?name=com.springsource.slf4j.api&version=1.6.1&searchType=bundlesByName&searchQuery=slf4j > ) > > look: > http://www.slf4j.org/codes.html#StaticLoggerBinder > ################## > > Failed to load class org.slf4j.impl.StaticLoggerBinder > > This error is reported when the org.slf4j.impl.StaticLoggerBinder class > could not be loaded into memory. This happens when no appropriate SLF4J > binding could be found on the class path. Placing one (and only one) of > slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or > logback-classic.jar on the class path should solve the problem. > > As of SLF4J version 1.6, in the absence of a binding, SLF4J will default to > a no-operation (NOP) logger implementation. > > ################## > > > > -------- Original Message -------- > Subject: Re: bundles fail to start --- > http://wiki.ops4j.org/display/paxlogging/2011/02/23/Pax+Logging+1.6.1+released > From: Guillaume Nodet <[email protected]> > To: Andrei Pozolotin <[email protected]> > Cc: General OPS4J <[email protected]> > Date: Sun 24 Apr 2011 01:38:33 AM CDT > > What classes do you use in this package? > > On Saturday, April 23, 2011, Andrei Pozolotin > <[email protected]> wrote: > > > > > > > Guillaume: > > > 1) thanks for the answer; > my current workaround is to mark slf4j-api maven dependency as optional; > > > 2) re: " > The org.slf4j.impl is not exported because it's not an API. Nobody is > supposed to use that directly. If you control the code, you can > simply remote the references to those. > Else, it may be a bit more complicated depending on how that's use. > > " > I am still not convinced; > > for example, if you take a look here: > http://ebr.springsource.com/repository/app/bundle/version/detail?name=com.springsource.slf4j.api&version=1.6.1&searchType=bundlesByName&searchQuery=slf4j > > it is still required (presumably spring people know what they are doing > :-) ) > > > > Package Name > Version Range > Optional? > > > org.slf4j.impl > [1.6.1, 2.0.0) > false > > > > > > 3) probably a better way to handle this in pax-logging would be: > > a) kill your org.ops4j.pax.logging.pax-logging-api_1.6.1.jar bundle > > b) let people use "normal" logging api bundle dependencies like this: > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>com.springsource > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com Connect at CamelOne May 24-26 The Open Source Integration Conference http://camelone.com/ _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
