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.
Re: Validation with external-noNamespaceSchemaLocation works with
   DTD, not wit

Re: Validation with external-noNamespaceSchemaLocation works with
   DTD, not wit

2004-02-23       - By Phil Weighill-Smith

Have you tried enabling the
"http://apache.org/xml/features/validation/schema" feature?

Phil :n.

On Mon, 2004-02-23 at 09:26, Pander wrote:

> Hi all,
>
> Validation (SAX and DOM) with external-noNamespaceSchemaLocation works with
> DTD, not with xsd schema (xerces 2.6.1).
>
> The following code bails out with an error on xsd schema but works fine with
> DTD. Problem is that with xsd, it does not realise that it has to deal with
> xsd, hence the error as can be seen below.
>
> Is this a bug or what has to be changed in the code to get this working?
>
> code
> ----
> import org.apache.xerces.parsers.DOMParser;
> import org.w3c.dom.Document;
>
> class validate {
>   public static void main(String[] args) {
>     try {
>       DOMParser aParser = new DOMParser();
>       aParser.setFeature
> ("http://xml.org/sax/features/validation", true);
>       aParser.setFeature
> ("http://apache.org/xml/features/continue-after-fatal-error", false);
>       aParser.setFeature
> ("http://apache.org/xml/features/validation/schema-full-checking", true);
>       aParser.setProperty
> ("http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation",
>           args[1]);
>       aParser.parse(args[0]);
>     } catch (Exception e) {
>       System.err.println("Exception caught in main: " +e);
>       System.exit(1);
>     }
>   }
> }
>
> compile
> -------
> javac -classpath xercesImpl.jar:xmlParserAPIs.jar validate.java
>
> files used in the next tests are from Xerces-J-bin.2.6.1.tar.gz from data
> directory
>
> correct run with DTD
> --------------------
> java -classpath .:xercesImpl.jar:xmlParserAPIs.jar validate personal.xml
> personal.dtd
>
> incorrect run with xsd schema
> -----------------------------
> java -classpath .;xercesImpl.jar;xmlParserAPIs.jar validate personal-
> schema.xml personal.xsd
>
> [Error] personal.xml:2:11: Document is invalid: no grammar found.
> [Error] personal.xml:2:11: Document root element "personnel", must match
> DOCTYPE root "null".
>
> As mentioned before this code is not aware that it has to deal with xsd
> schema instead of DTD. How can this be fixed since the code example is in a
> lot of tutorials on the net.
>
> Thanks,
>
> Pander
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
> For additional commands, e-mail: xerces-j-user-help@(protected)

--
Phil Weighill-Smith <phil.weighill-smith@(protected)>
Volantis Systems

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
 <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9">
</HEAD>
<BODY>
Have you tried enabling the &quot;http://apache.org/xml/features/validation
/schema&quot; feature?<BR>
<BR>
Phil :n.<BR>
<BR>
On Mon, 2004-02-23 at 09:26, Pander wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#737373"><I>Hi all,

Validation (SAX and DOM) with external-noNamespaceSchemaLocation works with
DTD, not with xsd schema (xerces 2.6.1).

The following code bails out with an error on xsd schema but works fine with
DTD. Problem is that with xsd, it does not realise that it has to deal with
xsd, hence the error as can be seen below.

Is this a bug or what has to be changed in the code to get this working?

code
----
import org.apache.xerces.parsers.DOMParser;
import org.w3c.dom.Document;

class validate {
  public static void main(String[] args) {
    try {
      DOMParser aParser = new DOMParser();
      aParser.setFeature
(&quot;</FONT><A HREF="http://xml.org/sax/features/validation"><U>http://xml
.org/sax/features/validation&quot;</U></A><FONT COLOR="#737373">, true);
      aParser.setFeature
(&quot;</FONT><A HREF="http://apache.org/xml/features/continue-after-fatal
-error"><U>http://apache.org/xml/features/continue-after-fatal-error&quot;</U><
/A><FONT COLOR="#737373">, false);
      aParser.setFeature
(&quot;</FONT><A HREF="http://apache.org/xml/features/validation/schema-full
-checking"><U>http://apache.org/xml/features/validation/schema-full-checking
&quot;</U></A><FONT COLOR="#737373">, true);
      aParser.setProperty
(&quot;</FONT><A HREF="http://apache.org/xml/properties/schema/external
-noNamespaceSchemaLocation"><U>http://apache.org/xml/properties/schema/external
-noNamespaceSchemaLocation&quot;</U></A><FONT COLOR="#737373">,
          args[1]);
      aParser.parse(args[0]);
    } catch (Exception e) {
      System.err.println(&quot;Exception caught in main: &quot; +e);
      System.exit(1);
    }
  }
}

compile
-------
javac -classpath xercesImpl.jar:xmlParserAPIs.jar validate.java

files used in the next tests are from Xerces-J-bin.2.6.1.tar.gz from data
directory

correct run with DTD
--------------------
java -classpath .:xercesImpl.jar:xmlParserAPIs.jar validate personal.xml
personal.dtd

incorrect run with xsd schema
-----------------------------
java -classpath .;xercesImpl.jar;xmlParserAPIs.jar validate personal-
schema.xml personal.xsd

[Error] personal.xml:2:11: Document is invalid: no grammar found.
[Error] personal.xml:2:11: Document root element &quot;personnel&quot;, must
match
DOCTYPE root &quot;null&quot;.

As mentioned before this code is not aware that it has to deal with xsd
schema instead of DTD. How can this be fixed since the code example is in a
lot of tutorials on the net.

Thanks,

Pander

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: </FONT><A HREF="mailto:xerces-j-user-help@(protected)
.apache.org">xerces-j-user-help@(protected)</I></A></PRE>
</BLOCKQUOTE>
<PRE><TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Phil Weighill-Smith &lt;<A HREF="mailto:phil.weighill-smith@(protected)"><U
>phil.weighill-smith@(protected)</U></A>&gt;<BR>
Volantis Systems
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>