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.
Validating with external entities and schemas 1.4.4 vs 2.3.0

Validating with external entities and schemas 1.4.4 vs 2.3.0

2003-02-21       - By Fitzharris, Walter M. (LNG-DAY)
Reply:     1     2     3  

For more on the same problem, see my unanswered emails in the archives...

To save you some pain:
Basically, schema does not address physical doc items like entities...they
are like word-processor macros that live in the physical world, not the
logical.

Schema addresses the logical doc, so entities beyond the built-in must be
pre-processed out by you before the parser ever sees the file.

My guess is that the mutant "combo" document worked with old versions of the
parser by pure luck.  Unfortunately, the default parser in XML Spy also
parses these Frankensteins without errors, giving you the illusion that you
might be able to use such a thing in production.


Walt Fitzharris

-----Original Message-----
From: Stottlemyer, Carl [mailto:carl.stottlemyer@(protected)]
Sent: Friday, February 21, 2003 9:19 AM
To: xerces-j-user@(protected)
Subject: Validating with external entities and schemas 1.4.4 vs 2.3.0



I have a document with structure similar to the xml below.  When I use
Xerces 1.4.4, I am able to validate the document against the schema without
any problems.  When I use Xerces 2.3.0 the validation tells me that all of
the elements in each of the entities need to be defined (however they are
defined in the schema.)  It appears to me that the xerces is searching the
DTD for the ANY elements without referencing the schema.  Any explanation as
to why it works in 1.4.4 and not 2.3.0.  I would also appreciate any
recommendations as to what I need to do to make it work in 2.3.0.

Thanks, Carl

<?xml version="1.0" encoding="UTF-8" ?>
<!-- leagues are validated against the league.xsd schema.
The DOCTYPE is included to provide ENTITY references to embedded xml files
-->
<!DOCTYPE league[
   <!ELEMENT league ANY>
  <!ENTITY team1 SYSTEM "someUrl">    
  <!ENTITY team2 SYSTEM "someUrl2">

]>
<leauge   xmlns=" http://www.myLeague.com <http://www.myLeague.com> "
 xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance> "
 xsi:schemaLocation=" http://www.myLeague.com <http://www.myLeague.com>  
                     someUrl3">
&team1;
&team2;
</league>


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Validating with external entities and schemas 1.4.4 vs 2.3.0</TITLE>

<META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=984011315-21022003><FONT face=Tahoma color=#0000ff size=4>For
more on the same problem, see my unanswered emails in the
archives...</FONT></SPAN></DIV>
<DIV><SPAN class=984011315-21022003><FONT face=Tahoma color=#0000ff
size=4></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=984011315-21022003><FONT face=Tahoma color=#0000ff size=4><U
>To
save you some pain:</U></FONT></SPAN></DIV>
<DIV><SPAN class=984011315-21022003><FONT face=Tahoma color=#0000ff
size=4>Basically, schema does not address physical doc items like
entities...they are </FONT></SPAN><SPAN class=984011315-21022003><FONT
face=Tahoma color=#0000ff size=4>like word-processor macros that live in the
physical world, not the logical.</FONT></SPAN></DIV>
<DIV><SPAN class=984011315-21022003><FONT face=Tahoma color=#0000ff
size=4></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=984011315-21022003><FONT face=Tahoma color=#0000ff
size=4>Schema addresses the logical doc, so entities beyond the built-in
</FONT></SPAN><SPAN class=984011315-21022003><FONT face=Tahoma color=#0000ff
size=4>must be pre-processed out by you before the parser ever sees the
file.</FONT></SPAN></DIV>
<DIV><SPAN class=984011315-21022003><FONT face=Tahoma color=#0000ff
size=4></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=984011315-21022003><FONT face=Tahoma color=#0000ff size=4>My
guess is that the mutant&nbsp;"combo" document&nbsp;worked with old versions of
the parser by pure luck.&nbsp; Unfortunately, the default parser in XML Spy
also
parses these Frankensteins without errors, giving you the illusion that you
might be able to use such a thing in production.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV>
<P><I><FONT face="Comic Sans MS" color=#0000ff>Walt Fitzharris</FONT></I> </P>
<P class=MsoNormal
style="MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Stottlemyer, Carl
[mailto:carl.stottlemyer@(protected)]<BR><B>Sent:</B> Friday, February 21, 2003
9:19 AM<BR><B>To:</B> xerces-j-user@(protected)<BR><B>Subject:</B>
Validating
with external entities and schemas 1.4.4 vs 2.3.0<BR><BR></P></FONT>
<P><FONT face=Arial size=2>I have a document with structure similar to the xml
below.&nbsp; When I use Xerces 1.4.4, I am able to validate the document
against
the schema without any problems.&nbsp; When I use Xerces 2.3.0 the validation
tells me that all of the elements in each of the entities need to be defined
(however they are defined in the schema.)&nbsp; It appears to me that the
xerces
is searching the DTD for the ANY elements without referencing the schema.&nbsp;
Any explanation as to why it works in 1.4.4 and not 2.3.0.&nbsp; I would also
appreciate any recommendations as to what I need to do to make it work in
2.3.0.</FONT></P>
<P><FONT face=Arial size=2>Thanks, Carl</FONT> </P>
<P><FONT face=Arial size=2>&lt;?xml version="1.0" encoding="UTF-8" ?&gt;</FONT>
<BR><FONT face=Arial size=2>&lt;!-- leagues are validated against the league
.xsd
schema.</FONT> <BR><FONT face=Arial size=2>The DOCTYPE is included to provide
ENTITY references to embedded xml files</FONT> <BR><FONT face=Arial
size=2>--&gt;</FONT> <BR><FONT face=Arial size=2>&lt;!DOCTYPE league[</FONT>
<BR><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; &lt;!ELEMENT league
ANY&gt;</FONT> <BR><FONT face=Arial size=2>&nbsp;&nbsp; &lt;!ENTITY team1
SYSTEM
"someUrl"&gt;&nbsp;&nbsp;&nbsp;&nbsp; </FONT><BR><FONT face=Arial
size=2>&nbsp;&nbsp; &lt;!ENTITY team2 SYSTEM
"someUrl2"&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</FONT><BR><FONT face=Arial size=2>]&gt;</FONT> <BR><FONT face=Arial
size=2>&lt;leauge&nbsp;&nbsp; xmlns="<A href="http://www.myLeague.com"
target=_blank>http://www.myLeague.com</A>"</FONT> <BR><FONT face=Arial
size=2>&nbsp; xmlns:xsi="<A href="http://www.w3.org/2001/XMLSchema-instance"
target=_blank>http://www.w3.org/2001/XMLSchema-instance</A>"</FONT> <BR><FONT
face=Arial size=2>&nbsp; xsi:schemaLocation="<A href="http://www.myLeague.com"
target=_blank>http://www.myLeague.com</A></FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT face=Arial
size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; someUrl3"&gt;</FONT> <BR><FONT face=Arial
size=2>&amp;team1;</FONT> <BR><FONT face=Arial size=2>&amp;team2;</FONT>
<BR><FONT face=Arial size=2>&lt;/league&gt;</FONT> </P></BODY></HTML>