> Unless I am missing something, there is a lot more to this than throwing
> an exception when the config file is not found. Most notable, throwing
> exceptions in a method that hid them previously breaks backward
compatibility.
That's right. That's the price to pay.
You have to decide what you value more: Compatibility or ability - being
backward compatible or being able to learn of any problem configuring log4j.
In my application I try to configure the patched (enhanced) log4j with a
DOMConfigurator first, and if that fails I use a BasicConfigurator with some
more or less reasonable defaults. Works well!
> On the other hand you are right to insist. :-) Ceki
:-)
--
Best regards
Rainer Klute
Dipl.-Inform. E-Mail: [EMAIL PROTECTED]
Rainer Klute Tel.: (0172) 2324824
Körner Grund 24 (0231) 511693
D-44143 Dortmund Fax: (0231) 511809
Sent through GMX FreeMail - http://www.gmx.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
