So I've been porting some of our services to use Logback over log4j and I've
been using the log4j-over-slf4j jar to spoof log4j for our legacy dependencies.
The only issue is log4j-over-slf4j doesn't implement many of the classes of
log4j so I'm seeing a decent few class not found exceptions from dependent
jars. How have people got around this? Is it enough to just put the nlog4j in
your classpath instead of the log4j-over-slf4j jar? I’d still like to use
one logback config file to drive all my logging to a single log file. Thanks.
jt
_______________________________________________
This e-mail may contain
information that is confidential, privileged or otherwise protected from
disclosure. If you are not an intended recipient of this e-mail, do not
duplicate or redistribute it by any means. Please delete it and any attachments
and notify the sender that you have received it in error. Unless specifically
indicated, this e-mail is not an offer to buy or sell or a solicitation to buy
or sell any securities, investment products or other financial product or
service, an official confirmation of any transaction, or an official statement
of Barclays. Any views or opinions presented are solely those of the author and
do not necessarily represent those of Barclays. This e-mail is subject to terms
available at the following link: www.barcap.com/emaildisclaimer.
By messaging
with Barclays you consent to the foregoing. Barclays Capital is the investment
banking division of Barclays Bank PLC, a company registered in
_______________________________________________