Well, isn't this enough already :-) You might want to highlight why this is so important: various libs use different logging libs; with pax-logging you can "gather" them all together in one log file needing only one implementation.
Kind regards, Andreas On Wed, Nov 30, 2011 at 20:55, Matt Madhavan <[email protected]> wrote: > 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 [email protected] http://lists.ops4j.org/mailman/listinfo/general
