Hi Niclas,
thanks for the info, I wasn't aware of the problem. I understood the basic problem is the way JCL dynamically determines the user's preferred logging implementation. What if the JCL configuration attribute ||org.apache.commmons.logging.Log is set which specifies the logging implementation to be used? Then there is no dynamic checking of available logging implemenations.
Regards Michael
On Thursday 10 February 2005 23:34, [EMAIL PROTECTED] wrote:
using the apache commons logging API
NO!!!
Please read; http://www.qos.ch/logging/classloader.jsp
JCL can be made working in simple/flat applications, but becomes impossible for server containers to deal with.
Please consult directly with Apache's logging expert Ceki G�lc� <[EMAIL PROTECTED]> and the logging.apache.org community, for instance on the [email protected] mailing list.
Thanks
Niclas
-- Michael Bouschen [EMAIL PROTECTED] Engineering GmbH mailto:[EMAIL PROTECTED] http://www.tech.spree.de/ Tel.:++49/30/235 520-33 Buelowstr. 66 Fax.:++49/30/2175 2012 D-10783 Berlin
