Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Exception when parsing from InputSource

Exception when parsing from InputSource

2004-02-12       - By W. Nathaniel Mills, III

In the xerces.jar that ships with WSAD 5.1 (C:\wsad51\eclipse\plugins\org
.apache.xerces_4.0.13\xercesImpl.jar (1,176,093 bytes), I've found the parser
doesn't appear to handle the end of inputsource correctly, when it is
constructed from a String, throwing an exception where the line number is -1.
I've coded a workaround, but wondered if this is known and fixed, or if there
is a better way to deal with this issue.

public void instantiateFrom(String strXML, ArrayList retList)
 throws XYZException {

 StringReader reader = new StringReader(strXML);
 InputSource inputSource = new InputSource(reader);

 m_List = retList;
 m_Parser.setContentHandler(this);
 m_Parser.setErrorHandler(this);
 try {
   m_Parser.parse(inputSource);
 } catch (SAXParseException e) {
  // handle end of file
  if (e.getLineNumber() != -1) {
    throw new XYZException(formatSAXParseException(e), e);
  } // else expected case due to reaching the end of the string
 } catch (SAXException e) {
   throw new XYZException(e.getLocalizedMessage(), e);
 } catch (IOException e) {
   throw new XYZException(e.getLocalizedMessage(), e);
 }
}

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY >
<DIV><FONT face="Courier New" size=-1>In the xerces.jar that ships with WSAD 5
.1
(C:\wsad51\eclipse\plugins\org.apache.xerces_4.0.13\xercesImpl.jar (1,176,093
bytes), I've found the parser doesn't appear to handle the end of inputsource
correctly, when it is constructed from a String, throwing an exception where
the
line number is -1.&nbsp; I've coded a workaround, but wondered if this is known
and fixed, or if there is a better way to deal with this issue.<BR><BR>public
void instantiateFrom(String strXML, ArrayList retList)<BR>&nbsp; throws
XYZException {</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face="Courier New" size=-1>&nbsp; StringReader reader = new
StringReader(strXML);<BR>&nbsp; InputSource inputSource = new
InputSource(reader);</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face="Courier New" size=-1>&nbsp; m_List = retList;<BR>&nbsp;
m_Parser.setContentHandler(this);<BR>&nbsp;
m_Parser.setErrorHandler(this);<BR>&nbsp; try {<BR>&nbsp;&nbsp;&nbsp;
m_Parser.parse(inputSource);<BR>&nbsp; } catch (SAXParseException e) {<BR>&nbsp
;
&nbsp;// handle end of file<BR>&nbsp; &nbsp;if (e.getLineNumber() != -1)
{<BR>&nbsp; &nbsp;&nbsp;&nbsp;throw new XYZException(formatSAXParseException(e)
,
e);<BR>&nbsp; &nbsp;} // else expected case due to reaching the end of the
string<BR>&nbsp; } catch (SAXException e) {<BR>&nbsp;&nbsp;&nbsp; throw new
XYZException(e.getLocalizedMessage(), e);<BR>&nbsp; } catch (IOException e)
{<BR>&nbsp;&nbsp;&nbsp; throw new XYZException(e.getLocalizedMessage(),
e);<BR>&nbsp; }<BR>}</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face="Courier New" size=-1></FONT>&nbsp;</DIV></BODY></HTML>