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.
Bug in 2.3.0? ClassCastException with ListDV$ListData

Bug in 2.3.0? ClassCastException with ListDV$ListData

2003-01-28       - By Aleksandar Milanovic
Reply:     1     2  

Hi Neil,

We're using JDK 1.4.0. Here's the debug info:

java.lang.ClassCastException: org.apache.xerces.impl.dv.xs.ListDV$ListData
  at
org.apache.xerces.impl.xs.XMLSchemaLoader.processExternalHints(XMLSchemaLoad
er.java:567)
  at
org.apache.xerces.impl.xs.XMLSchemaValidator.reset(XMLSchemaValidator.java:1
345)
  at
org.apache.xerces.parsers.BasicParserConfiguration.reset(BasicParserConfigur
ation.java:543)
  at
org.apache.xerces.parsers.DTDConfiguration.reset(DTDConfiguration.java:640)
  at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:512)
  at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:595)
  at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
  at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:253)
  at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:20
4)
  at
com.galdosinc.gds.validator.ValidatorDocumentBuilder.parse(ValidatorDocument
Builder.java:92)
  at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:86)

The erroneous use-case is as follows:

An instance document is validated as it is being parsed. We are using
external-schema-location property to specify the URLs of the schemas of
interest. A dummy entity resolver is used to ensure that the schemaLocation
in the instance document is ignored (by returning an empty string). However,
in this particular case the schemaLocation attribute is not even specified
in the instance document. Schemas are cached in a passive way, i.e. as they
are loaded from the URLs specified in external-schema-location. All schema
locations that appear in schema imports and includes are also valid URLs.
The instance document and all the referenced schemas are valid. This things
works well with previous versions of Xerces (2, 2.1 and 2.2).

Hope this helps. Let me know if you need more details.

Cheers,
Alex

> -----Original Message-----
> From: neilg@(protected) [mailto:neilg@(protected)]
> Sent: Tuesday, January 28, 2003 2:38 PM
> To: xerces-j-user@(protected)
> Subject: Re: Bug in 2.3.0?
>
>
> Hi Alex,
>
> Well, it's possible you've found a bug; I think it's fair to say that the
> xerces-specific schemaLocation properties don't tend to get tested as well
> as many other aspects of the parser...
>
> I'd recommend two things:
>
> 1.  Give us a cut-down test-case that reproduces the problem;
> 2.  If you can't do that, then at least recompile Xerces with
> debugging, so
> we at least have line numbers in the stack trace.
>
> Knowing what JDK you're on could also be important.
>
> Cheers,
> Neil
> Neil Graham
> XML Parser Development
> IBM Toronto Lab
> Phone:  905-413-3519, T/L 969-3519
> E-mail:  neilg@(protected)
>
>
>
>
> |---------+---------------------------->
> |         |           "Aleksandar      |
> |         |           Milanovic"       |
> |         |           <amilanovic@(protected)|
> |         |           sinc.com>        |
> |         |                            |
> |         |           01/28/2003 05:25 |
> |         |           PM               |
> |         |           Please respond to|
> |         |           xerces-j-user    |
> |         |                            |
> |---------+---------------------------->
>
> >-----------------------------------------------------------------
> ------------------------------------------------------------------
> ----------|
>   |
>
>             |
>   |       To:       "Xerces-J-User"
> <xerces-j-user@(protected)>
>                                           |
>   |       cc:
>
>             |
>   |       Subject:  Bug in 2.3.0?
>
>             |
>   |
>
>             |
>   |
>
>             |
>
> >-----------------------------------------------------------------
> ------------------------------------------------------------------
> ----------|
>
>
>
> Hi,
>
> We tried using Xerces 2.3.0 instead of 2.2.1 and got the following error:
>
> java.lang.ClassCastException: org.apache.xerces.impl.dv.xs.ListDV$ListData
>  at org.apache.xerces.impl.xs.XMLSchemaLoader.processExternalHints(Unknown
> Source)
>  at org.apache.xerces.impl.xs.XMLSchemaValidator.reset(Unknown Source)
>  at org.apache.xerces.parsers.BasicParserConfiguration.reset(Unknown
> Source)
>  at org.apache.xerces.parsers.DTDConfiguration.reset(Unknown Source)
>  at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
>  at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
>  at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>  at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
>  at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
>
> It's a bit confusing that a DTDConfiguration class shows up, because we
> don't use DTDs at all, only XML schemas.
>
> Any clue?
>
> thx
> Alex
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
> For additional commands, e-mail: xerces-j-user-help@(protected)
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
> For additional commands, e-mail: xerces-j-user-help@(protected)
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)