On Mon, Apr 25, 2011 at 18:56, Andrei Pozolotin <andrei.pozolo...@gmail.com> wrote: > Guillaume, hi: > when I started my evaluation of pax-logging, I had these expectations: > a) it would allow me to keep "normal" logging api, like slf4j-api, w/o > messing up dependencies;
That's actually true. You can use in your projects slf4j-api, log4j api, jul, jcl or whatever without needing a dependency on paxlogging. > b) it would allow me to swap/upgrade back end provider, like logback > instead of log4j, transparently; Right, that's not the case and not really the goal. > Now I see that I was wrong, sorry it took me this much time to understand > it. > I do not know if I will in fact use pax-logging or not, it is merely not > what I expected. > Thank you very much for your responses. > 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: Guillaume Nodet <gno...@gmail.com> > To: General OPS4J <general@lists.ops4j.org> > Date: Mon 25 Apr 2011 10:31:16 AM CDT > > Le lundi 25 avril 2011, Andrei Pozolotin <andrei.pozolo...@gmail.com> a > écrit : > > > > > > 1) it forces me to change maven dependencies for universal > (non-osgi-centric) artifacts; > > > Writing you own framework will have exactly the same effect. And i > don't think it's true anyway. You can keep dependencies on slf4j and > use paxlogging at runtime, that's not a problem. > > > > 2) it does not let me use logback; > > > Pax-Logging is a logging framework. If you want to use logback > instead, that's definitely a different option. But if you want to use > logback, I'm not sure why you looked at paxlooging in the first place, > it seems you don't have a choice to make anymore ;-) > > > > -------- 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 <gno...@gmail.com> <gno...@gmail.com> > To: General OPS4J <general@lists.ops4j.org> > Date: Mon 25 Apr 2011 01:52:32 AM CDT > > 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 <andrei.pozolo...@gmail.com> > 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 > <kowalewski.bart...@gmail.com> <kowalewski.bart...@gmail.com> > To: General OPS4J <general@lists.ops4j.org> <general@lists.ops4j.org> > 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 <andrei.pozolo...@gmail.com>: > > > 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 <gno...@gmail.com> > To: Andrei Pozolotin <andrei.pozolo...@gmail.com> > Cc: General OPS4J <general@lists.ops4j.org> > Date: Sun 24 Apr 2011 01:38:33 AM CDT > > What classes do you use in this package? > > O > > > > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > -- 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 general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
