On Jun 29, 2005, at 8:59 AM, Schuweiler, Joel J. wrote:
You're kidding right? I say it works because, well, and this is a toughie, it works. I just wanted to find out what was causing the error.
One of the design principles was that log4j should not introduce new failure modes for applications that use it. So if something goes wrong, a configuration files is missing or invalid, a file appender points to a non-existent location or is read-only, log4j doesn't stop the application from working. The downside of that is that problems with configuration files or other log4j-related problems are obscured.
In this case, the xml configuration file was invalid according to the DTD, a message to that effect was output to the console, but log4j trooped on.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
