Hi, When using Log4J with the DOMConfigurator, is there any way to spot (programmatically) that initialisation of Log4J has failed? If the Log4J configuration file is invalid, you get a "log4j:ERROR" on the standard error stream and then when you write messages to Log4J you get the message about no appenders being found, rather than the message, being written out. Is there any way for an application to be notified or to interrogate Log4J in order to establish that configuration failed? Thanks for any insights. Cheers, Eoin. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
