Hi,
I don't use nothing of it. My problem was, that one of the facades
throwed an exception, the other one didn't. How I learned later (that's
why read the f*** manual ;) this jar's are only facades to underlying
logging frameworks. Because I didn't use up to this point no logging
framework, the exception was thrown inside the facade. After adding the
log4 jar to my project, the issue was solved.
Regards
Michael
Ceki Gülcü wrote:
Hello Trustin,
Michael asks about the difference between the two cases. I really can't
think of any. Is he using Tomcat version 5.5.14 or 5.5.15 by any chance?
At 11:31 AM 4/12/2006, Trustin Lee wrote:
On 4/12/06, Michael Bauroth
<<mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED]> wrote:
Hi,
I figured out an exception while calling CharsetUtil.getDefaultCharset.
It took me a while until I found out, that the call of
LoggerFactory.getLogger( CharsetUtil.class ) failed. I've used the jar
slf4j-log4j13. After replacing it with slf4j-simple all works fine.
Now my question: What is the difference?
Could you please give us a stack trace?
Thanks,
Trustin
--
--
_____ Falcom Wireless Communications GmbH ______________________________
Dipl.-Ing. Michael Bauroth
Manager Software Department
Phone: +49 3677 8042 332
Fax: +49 3677 8042 215
E-mail: [EMAIL PROTECTED]
Address: Gewerbering 6, 98704 Langewiesen, Germany
______________________________ www.falcom.de ___________________________
This e-mail and any files transmitted are the property of FALCOM and/or
its affiliates, are confidential, and are intended solely for the use of
the individual or entity to whom this e-mail is addressed. If you are
not one of the named recipients or otherwise have reason to believe that
you have received this e-mail in error, please notify the sender and
delete this message immediately from your computer. Any other use,
retention, dissemination, forwarding, printing or copying of this e-mail
is strictly prohibited.
