Hi Matt, yep, that's pretty much it. it encapsulate all you need and it can be configured the OSGi way ;) through config-admin service (that's why it's still a log4j.property file, but well) and so much more you could also take a look at the closed jira's which might give you a hint of what kind of "improvements" where made. One that instantly crosses my mind was some sort of performance improvement :)
regards, Achim 2011/11/30 Matt Madhavan <mattmadha...@gmail.com> > Hello, > Sorry missing action for a while. Dealing with IBM WAS V7 and OSGi mess! > Still going through the mess-lost about 2 months on this. We have decided > to go with carefully designed EAR (Spring) then convert the projects to > OSGi after WAS V8 is approved by my client. > > Quick question please? > > What are the pros and cons between PAX logging ans the other solutions out > there including logback. My answer to my client was as follows: Is there > any thing more I can add to it? > > *Also lets just go with PAX Logging as it ancapsulates all the looging > like SLF4j, JCL, log4j, JDK, Avelon and also implementes the OSGi logging > service etc * > * > * > Thanks in advance! > > Matt > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/>
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
