Re: LoggerStore
Mauro Talevi <[email protected]>
| Newsgroups | gmane.comp.java.spice.devel |
|---|---|
| Message-ID | <[email protected]> |
>>You'll notice that the unit test fails on the Element constructor. > > > Ill have a look when I next get a chance. Configurator.buildElement() has been changed to have accept an optional EntityResolver and uses the java.xml.parsers directly rather than passing via a Configuration object. This allows a Log4jEntityResolver to be passed in and correctly resolve the log4j.dtd from the jar. This will work with xerces but not with Crimson parsers. For that a systemId "dummy://log4j.dtd" is required. All this should really be done by the log4j DOMConfigurator itself. I'll post a patch sometime soon, but for the moment the buildElement is generic enough. I've left in a buildElement( InputStream ) method as well which uses no EntityResolver and no systemId. ------------------------------------------------------- This SF.net email is sponsored by: If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge