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.
Problem validating schema based document with a <!DOCTYPE > declaration. (Followu

Problem validating schema based document with a <!DOCTYPE > declaration. (Followu

2003-07-18       - By Peter C. Chapin


In an earlier message I said:

> Hello!
>
> I have a document that starts out like this
>
> ---- cut here ----
> <?xml version="1.0"?>
>
> <!DOCTYPE observation-set [
>   <!ENTITY copy  "&#169;">
> ]>
>
> <observation-set
>  xmlns="http://www.ecet.vtc.edu/~pchapin/AOML_0.0"
>  xmlns:xhtml="http://www.w3.org/1999/xhtml"
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>  xsi:schemaLocation="http://www.ecet.vtc.edu/~pchapin/AOML_0.0
>    AOML.xsd">
>
>  <!-- etc -->
> </observation-set>
>
> ---- cut here ----

This document does not validate. However, if the <!DOCTYPE>
declaration is removed (along with the references to the
&copy; entity) the document validates fine. I now understand
why, but I don't know how to fix it.

I attempted to validate the document using the sax.Counter
sample program provided with Xerces-J. I also wrote a simple
program of my own to explore the issues. I turned on the
following features:

  http://xml.org/sax/features/validation
  http://apache.org/xml/features/validation/schema

It is my understanding that I need both of these features to
effect schema validation. However, the FAQ (in the Xerces-J
documentation) says:

Q: What happens if I set both validation and schema validation
features on?

A: ... if the instance document has both DTD and XML Schema
grammars, validation errors for both DTD and XML Schema are
reported...

In my case I need a DTD for the <!ENTITY> declaration. Thus
Xerces will report both DTD and XML Schema validation errors.
However since my DTD declares no elements, the DTD validation
process reports an "undeclared element" for every element in
my document. I noticed that if I inject a violation of the XML
Schema into the document then I get an error about that
violation in addition to all the "undeclared element" errors.
Thus it appears that the DTD validation and XML Schema
validation processes are occuring in parallel and largely
independently.

The FAQ in the Xerces documentation goes on:

Q: How can I tell the parser to validate against XML Schema
and not to report DTD validation errors?

A: Currently this is impossible. We hope that JAXP 1.2 will
provide this capability via its schema language property.

This would be a good time to state that I'm using Xerces-J
v2.4.0 and the "readme" section of the documentation implies
that JAXP 1.2 is supported. So the documentation seems
somewhat inconsistent, but I guess that's not a shocking
thing.

In any case, it appears that it is not possible to validate a
document based on an XML Schema and that uses <!DOCTYPE> only
for purposes of introducing entities. Is this really true? It
seems somewhat incredible but the FAQ in the documentation is
clear. The list of supported features does not seem to include
anything that would allow me to specify that only XML Schema
validation errors should be reported. Am I missing something?

Peter

P.S. I'm using j2sdk1.4.1


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