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.
Commented: (XERCESJ-1163) javax.xml.validation.Validator#validate impleme

Commented: (XERCESJ-1163) javax.xml.validation.Validator#validate impleme

2006-05-23       - By Ortwin Glück (JIRA)
Reply:     1     2     3     4  

   [ http://issues.apache.org/jira/browse/XERCESJ-1163?page=comments#action
_12412895 ]

Ortwin Glück commented on XERCESJ-1163:
---------------------------------------

Thanks Michael for this excellent explanation. I have a use case that is a bit
special and I am not sure if this is a Xerces or a JDOM problem.

I create a JDOM with all nodes in NO_NAMESPACE (structure is defined by
customer). This JDOM is subsequently converted to a Xerces DOM with the JDOM's
DOMOutputter. This would use Document.createElement instead of Document
.createElementNS to create the Elements for example as I use NO_NAMESPACE. This
way I always get a DOM without namespace support. Now I want to validate this
DOM against a schema (provided by the customer). The schema does not declare a
target namespace. And the XML files reference it with noNamespaceSchemaLocation
. This seems legal to me. But with no namespace support in the DOM I can not use
the schema validation due to this issue.

Would it be possible to use createElementNS instead here, even though I have no
namespace? Then it can be solved in JDOM's DOMOutputter.
If not, then you should think about how to validate a DOM with no namespace :-)

> javax.xml.validation.Validator#validate implementation does not support a
DOMSource argument
> -----------------------------------------------------------------------------
---------------
>
>          Key: XERCESJ-1163
>          URL: http://issues.apache.org/jira/browse/XERCESJ-1163
>      Project: Xerces2-J
>         Type: Bug

>   Components: JAXP (javax.xml.validation)
>     Versions: 2.8.0
>     Reporter: Steven Grossman

>
> Validator#validate implementation does not support a DOMSource argument.  The
following SAXParseException is always thrown:
> Exception in thread "main" org.xml.sax.SAXParseException: cvc-elt.1: Cannot
find the declaration of element 'xxx'.
> The problem is not seen in the 1.5 jdk.
> I've supplied a test class that succesfully validates an xml instance
document using a StreamSource and subsequently fails to perform the validation
against a DOMSource representation of the same xml.
> import java.io.StringReader;
> import java.io.IOException;
> import javax.xml.XMLConstants;
> import javax.xml.parsers.DocumentBuilder;
> import javax.xml.parsers.DocumentBuilderFactory;
> import javax.xml.parsers.ParserConfigurationException;
> import javax.xml.transform.stream.StreamSource;
> import javax.xml.transform.dom.DOMSource;
> import javax.xml.validation.Schema;
> import javax.xml.validation.SchemaFactory;
> import javax.xml.validation.Validator;
> import org.xml.sax.SAXException;
> import org.xml.sax.InputSource;
> import org.w3c.dom.Document;
> public final class ValidatorBug {
>     private static final String SCHEMA >         "<?xml version=\"1.0\"
encoding=\"UTF-8\"?>\n" +
>         "<xs:schema xmlns:xs=\"http://www.w3.org/2001/XMLSchema\"
elementFormDefault=\"qualified\" attributeFormDefault=\"unqualified\">\n" +
>         "    <xs:element name=\"root\"/>\n" +
>         "</xs:schema>";
>     private static final String XML = "<?xml version=\"1.0\" encoding=\"UTF-8
\"?><root/>";
>     public static void main(String[] args) throws SAXException, IOException,
ParserConfigurationException {
>         SchemaFactory schemaFactory >                 SchemaFactory
.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);
>         Schema schema = schemaFactory.newSchema(new StreamSource(new
StringReader(SCHEMA)));
>         Validator validator = schema.newValidator();
>         System.out.println("\nvalidating stream source");
>         validator.validate(new StreamSource(new StringReader(XML)));  // <---
WORKS
>         System.out.println("valid");
>         DocumentBuilderFactory documentBuilderFactory =
DocumentBuilderFactory.newInstance();
>         DocumentBuilder documentBuilder = documentBuilderFactory
.newDocumentBuilder();
>         Document document = documentBuilder.parse(new InputSource(new
StringReader(XML)));
>         System.out.println("\nvalidating DOM source");
>         validator.validate(new DOMSource(document));   // <--- PROBLEM
>         System.out.println("valid");
>     }
> }
> The exception:
> Exception in thread "main" org.xml.sax.SAXParseException: cvc-elt.1: Cannot
find the declaration of element 'root'.
>   at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException
(Unknown Source)
>   at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>   at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown
Source)
>   at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
>   at org.apache.xerces.jaxp.validation.DOMValidatorHelper.beginNode(Unknown
Source)
>   at org.apache.xerces.jaxp.validation.DOMValidatorHelper.validate(Unknown
Source)
>   at org.apache.xerces.jaxp.validation.DOMValidatorHelper.validate(Unknown
Source)
>   at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(Unknown Source)
>   at javax.xml.validation.Validator.validate(Validator.java:82)
>   at ValidatorBug.main(ValidatorBug.java:42)
> (This bug is represented by XERCESJ-1132 and XERCESJ-1161, but they were in
the wrong component)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
  http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
  http://www.atlassian.com/software/jira


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