https://issues.apache.org/bugzilla/show_bug.cgi?id=47671
--- Comment #3 from Earl Hood <[email protected]> 2009-08-11 08:00:03 PDT --- (In reply to comment #2) > resolveSystem(file:/files/erlang/module.xsl) > resolveSystem(file:/files/erlang/erlang.xml) > resolveSystem(file:/files/erlang/erlref.dtd) The above verbosity implies (to me) that the parser is passing the wrong system ID to the resolver. I.e. Instead of the XML parser passing just "erlref.dtd" to the resolver, the parser is first fully qualifying the system ID (probably based upon the current working directory) before it passes the system ID to the resolver. Since the catalog has no entry for "file:/files/erlang/erlref.dtd", the resolver will find no matching entries. The parser then attempts to load the file directory, which of course fails since the file does not exist with given path. At this time, this appears to be an XML parser problem. The parser should only be passing "erlref.dtd" to the resolver. BTW, did you trim some of the diagnostic output? It seems the XML parser is calling Catalog directly versus the CatalogResolver class that implements the SAX EntityResolver and JAXP URIResolver interfances. I see no debugging messages from the CatalogResolver class. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
