Paul, Is it possible that your configuration file had/has a different value for "log4j.dtd" in the DOCTYPE?
-Mark > -----Original Message----- > From: Paul Austin [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 08, 2002 3:30 PM > To: Log4J Developers List > Subject: RE: DomConfigurator Entity Resolver update > > > Guys, > > The original error was reported in the following bug > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12366 which > shows the > stack trace from someone else's application. The error below > was the same as > the one I was receiving. > > log4j:ERROR Could not parse input source > [org.xml.sax.InputSource@cd107f]. > java.net.MalformedURLException: no protocol: log4j.dtd > at java.net.URL.<init>(URL.java:579) > : > <snip> > : > at > org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuild > erImpl.java:20 > 1) > at > org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurat > or.java:672) > > I have tried to reproduce the error again but can't get our > application back > to the same set of libraries that produced the orginal > problem, with lots of > trying today (I knew I should have designed a test case at > that point). > > Anyway the approach provided in the fix is the correct way to > look up a dtd > using the JAXP apis and should be supported by all parsers. > > Also as mentioned before using this approach you can start to > support using > a public id for the log4j.dtd file. > > Paul > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
