I've been getting a SAXParseException (once I knew where to get the stack trace) using Joran with an existing log4j config file, but the error wasn't being propagated.
I can't see how the ExecutionContext is propagating the error list. It doesn't look like anything calls ConfiguratorBase.dumpErrors or anything that could report startup config failure is getting the error list from the ExecutionContext. By the way, for those with existing log4j xml config files, the system may act as if it couldn't find your config. Here's the reason: org.xml.sax.SAXParseException: Relative URI "log4j.dtd"; can not be resolved without a base URI. I have the -Dlog4j.debug=true in my script. I thought I saw something on the list about having to change existing config files with 1.3 alpha. I'll go through the archives and see if something pops up, but if someone knows how to fix this (Ceki?) I'd appreciate hearing how. Thanks Scott
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
