Bug 15871 - External DTD connect Error
Summary: External DTD connect Error
Status: NEW
Alias: None
Product: Xerces-J
Classification: Unclassified
Component: DTD (show other bugs)
Version: 1.4.4
Hardware: PC All
: P3 normal
Target Milestone: ---
Assignee: Xerces-J Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-07 22:38 UTC by subbu kalyanasundaram
Modified: 2005-03-20 17:06 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description subbu kalyanasundaram 2003-01-07 22:38:41 UTC 
In the XML if we have newline charcter in the http portion of the SYSTEM id, we 
are getting the following "File not found error"

Example:

Working One:
<!DOCTYPE AbPortRequest 
SYSTEM "http://roswell.com/03/systemDTDs/AbAssignRequest.dtd">

<!DOCTYPE AbPortRequest SYSTEM "http://roswell.com/03/systemDTDs/
AbAssignRequest.dtd">

That is if "http:..." has a new line character, the parser does not ignore the 
newline character.  This works in other XML Editors.

Error :

        at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1219
)
        at org.apache.xerces.readers.DefaultEntityHandler.startReadingFromExtern
alEntity(DefaultEntityHandler.java:780)
        at org.apache.xerces.readers.DefaultEntityHandler.startReadingFromExtern
alSubset(DefaultEntityHandler.java:571)
        at org.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScann
er.java:1139)
        at org.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDoc
umentScanner.java:2145)
        at org.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentSc
anner.java:2100)
        at org.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispa
tch(XMLDocumentScanner.java:831)
        at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentS
canner.java:381)
Comment 1 Neil Graham 2003-01-13 16:58:04 UTC 
Although you may believe you're using Xerces 2.2.1, the stack trace you've 
provided shows you're actually using some version of Xerces1.  Whether this 
problem proves to exists or not in Xerces2, you should consider upgrading; no 
work has been done on Xerces1 in well over a year...