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.
handling of unresolved grammar in preparsing

handling of unresolved grammar in preparsing

2004-04-24       - By Jeff Greif
Reply:     1     2  

In preparsing this schema which contains an unresolvable namespace

<schema xmlns:bogus="http://hyperspace/"
            xmlns="http://www.w3.org/2001/XMLSchema"
            targetNamespace="http://example.com/ns">
 <complexType name="RootType">
    <sequence>
       <element name="ok" type="string"/>
       <element name="bad" type="bogus:Random"/>
   </sequence>
 </complexType>
</schema>

using Xerces 2.2.1 (I know, there is a later, better version), I get behavior
that is not what I want when I supply an entity resolver to the preparser.  If
the entity resolver returns null, a non-null grammar is returned from the
preparse, and when I create an XSModel from that grammar, there is an anyType
node in place of the type that cannot be resolved.  What I want is to have an
exception thrown, or better, a null grammar returned.  Is there a feature or
property that can be set on the preparser to achieve this?  If not in 2.2.1, is
there such a feature or property in later versions of Xerces?

Note that in xerces 2.2.1, I can get the desired behavior by supplying no
entity resolver.  In that case, XmlSchemaLoader.resolveDocument() throws a
NullPointerException, which would probably be considered a bug, but for me, it
's a feature!

Jeff


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Verdana size=2>In preparsing this schema which contains an
unresolvable namespace</FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Verdana size=2>&lt;schema xmlns:bogus="<A
href="http://hyperspace/">http://hyperspace/</A>"</FONT></DIV>
<DIV><FONT face=Verdana
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
xmlns="http://www.w3.org/2001/XMLSchema"</FONT></DIV>
<DIV><FONT face=Verdana
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;targetNamespace="http://example.com/ns"&gt;</FONT></DIV>
<DIV><FONT face=Verdana size=2>&nbsp; &lt;complexType
name="RootType"&gt;</FONT></DIV>
<DIV><FONT face=Verdana size=2>&nbsp;&nbsp;&nbsp;&nbsp;
&lt;sequence&gt;</FONT></DIV>
<DIV><FONT face=Verdana size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;element name="ok" type="string"/&gt;</FONT></DIV>
<DIV><FONT face=Verdana size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;element name="bad" type="bogus:Random"/&gt;</FONT></DIV>
<DIV><FONT face=Verdana size=2>&nbsp;&nbsp;&nbsp; &lt;/sequence&gt;</FONT></DIV>
<DIV><FONT face=Verdana size=2>&nbsp; &lt;/complexType&gt;</FONT></DIV>
<DIV><FONT face=Verdana size=2>&lt;/schema&gt;</FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Verdana size=2>using Xerces 2.2.1 (I know, there is a later,
better version), I get behavior that is not what I want when I supply an entity
resolver to the preparser.&nbsp; If the entity resolver returns null, a non
-null
grammar is returned from the preparse, and when I create an XSModel from that
grammar, there is an anyType node in place of the type that cannot be
resolved.&nbsp; What I want is to have an exception thrown, or better, a null
grammar returned.&nbsp; Is there a feature or property that can be set on the
preparser to achieve this?&nbsp; If not in 2.2.1, is there such a feature or
property in later versions of Xerces?</FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Verdana size=2>Note that in xerces 2.2.1, I can get the desired
behavior by supplying no entity resolver.&nbsp; In that case,
XmlSchemaLoader.resolveDocument() throws a NullPointerException, which would
probably be considered a bug, but for me, it's a feature!</FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Verdana size=2>Jeff</FONT></DIV>
<DIV><FONT face=Verdana size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Verdana size=2></FONT>&nbsp;</DIV></BODY></HTML>