xerces not parsing elements correctly

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

xerces not parsing elements correctly

xerces not parsing elements correctly

2003-05-02 - By Malia Zaheer

Reply: 1 2 3

I am using xerces to parse an xml file containing the element:
<ldap.username>uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeR
oot</ldap.username>

But, the parser is deleting some characters while parsing the string and I
get this:

uid=admin,ou=Administrators,ou=ologyManagement,o=NetscapeRoot

Notice the Top in TopologyManagement is missing and I get ologyManagement.
This has happened with another element in the same file.

<ldap.organization>uid=UShasta,ou=People,o=technicacorp.com</ldap.organizati
on>

In that case, the parser omitted "uid=UShasta," from the element and I got

<ldap.organization>ou=People,o=technicacorp.com</ldap.organization>

I figured this problem and just moved that element above another element and
things started working. Now I am getting similar error and I don't want to
kluge the system by finding a workaround. I think this is a bug with
Xerces. I don't know what could be causing this because this error happens
only sometimes, not always. The last time it happened, it consistently gave
me that error until I move the element around, but after that, it didn't
happened for about 3 weeks. I am using Xerces 2.0.0.

Thanks,

Malia

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">

<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>

</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

I am using xerces to parse an xml file containing the
element:
<ldap.username>uid=admin,ou=Administrators,ou=TopologyManagement,o
=NetscapeRoot</ldap.username>

 

But, the parser is deleting some characters while parsing
the string and I get this:

 

uid=admin,ou=Administrators,ou=ologyManagement,o
=NetscapeRoot

 

Notice the Top in TopologyManagement is missing and I get
ologyManagement. 
This has happened with another element in the same file.

 

<ldap.organization>uid=UShasta,ou=People,o
=technicacorp.com</ldap.organization>

 

In that case, the parser omitted "uid=UShasta,"  from
the element and I got

 

<ldap.organization>ou=People,o=technicacorp.com<
/ldap.organization>

 

I figured this problem and just moved that element above
another element and things started working.  Now I am getting similar error
and I don't want to kluge the system by finding a workaround.  I
think this is a bug with Xerces.  I don't know what could be causing
this because this error happens only sometimes, not always.  The last time
it happened, it consistently gave me that error until I move the element around,
but after that, it didn't happened for about 3 weeks.  I am using
Xerces 2.0.0.

 

Thanks,

Malia

 

</div>

</body>

</html>