DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25333>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25333

org.xml.sax.SAXParseException: File "E:\SD_ToolKit\xml\trading\dtd\B2BProductSet.dtd" 
not found even though the file exists.

           Summary: org.xml.sax.SAXParseException: File
                    "E:\SD_ToolKit\xml\trading\dtd\B2BProductSet.dtd" not
                    found even though the file exists.
           Product: Xerces2-J
           Version: 2.4.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: SAX
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Please forward this question...

Occasionally I get the following exception although the dtd file exists.  This
does not happen all the time but it seems to happen more often when using a
newer version of the xerces parser.  Is there a none problem with a new
implementation or a way to get more information since the exception does not
tell us enough and the message it is telling us is not correct because the file
exists.

org.xml.sax.SAXParseException: File
"E:\SD_ToolKit\xml\trading\dtd\B2BProductSet.dtd" not found. 

when calling 

DocumentBuilderFactory bldrFactory = DocumentBuilderFactory.newInstance(); 
bldrFactory.setValidating(true); 
                
XMLEntityResolver entityResolver = new
XMLEntityResolver("E:\SD_ToolKit\xml\trading\dtd"); 
DocumentBuilder parser = bldrFactory.newDocumentBuilder(); 
parser.setEntityResolver(entityResolver); 
StringReader xmlInput = new StringReader(getProductSetXml()); 
DocumentBuilder..parse(new org.xml.sax.InputSource(xmlInput)); 

The file exists in the directory stated in the exception.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to