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.
Validator features

Validator features

2006-12-11       - By Michael Glavassevich
Reply:     1     2     3     4  

kris2006 <admin@(protected)> wrote on 12/11/2006 07:21:33 PM:

> Michael,
>
> Thank you for your lightning response.
>
> I was able to cast my jaxp Validator object as a PSVIProvider, in theory
> giving me access to the getElementPSVI() methods to find the value of
> validationAttempted, as you've suggested. However, getElementPSVI()
returns
> a null, I presume since it is only valid within the start/end of the
> element, and I am simply using:
>
> ...
> Schema schema = schemaFactory.newSchema(schemaSource);
> Validator validator = schema.newValidator();
> validator.validate(streamSource);
>
> and so no longer have a context for getElementPSVI().

Right. Specifically the Javadoc [1] for getElementPSVI() says: "The method
must be called by an application while in the scope of the methods which
report the start and end of an element. For example, for SAX the method
must be called within the scope of the document handler's startElement or
endElement call. If the method is called outside of the specified scope,
the return value is undefined."

> Any idea how do I could return a valid ElementPSVI?

So you need to write a SAX content handler which receives the output from
the Validator (SAXSource/SAXResult) or ValidatorHandler. Within the scope
of the startElement/endElement callbacks of your content handler you would
query the PSVIProvider.

> Thanks again for your help...
>
> Regards,
> Kris

[1]
http://xerces.apache.org/xerces2-j/javadocs/xs/org/apache/xerces/xs
/PSVIProvider.html#getElementPSVI()

> Michael Glavassevich wrote:
> >
> > kris2006 <admin@(protected)> wrote on 12/07/2006 12:28:21 AM:
> >
> >> I am looking for the set of valid Features for the Xerces
implementation
> > of
> >> the JAXP Validator class. The Features described in
> >> http://xerces.apache.org/xerces2-j/features.html pertain to
> > DocumentBuilder
> >> and SAXParser.
> >
> > That's been on my TODO list for awhile. Just haven't been finding the
time
> > to write it up.
> >
> >> I have tried using one of the general features listed there
> >>
(http://apache.org/xml/features/validation/warn-on-undeclared-elemdef)
> > but
> >> it is not recognised for either Validator or SchemaFactory classes.
> >
> > That feature only applies to DTDs. It warns [1] you when the content
model
> > of an element declaration references an element which has not been
> > declared in the DTD.
> >
> >> In particular I would like to validate a soap envelope that contains
a
> > xml
> >> string as its body - using both the SOAP-ENV schema and the relevant
> > schema
> >> of the enveloped xml. This works, but if the wrong schema is
specified
> > for
> >> the enveloped xml the soap still validates! I think the feature
> > mentioned
> >> above would warn if the schema was incorrect and so would solve my
> > problem.
> >> Any other suggestions appreciated...
> >
> > You should examine the PSVI [2] if you want to check the degree [3] to

> > which the SOAP message was validated.
> >
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
> >> For additional commands, e-mail: j-dev-help@(protected)
> >
> > [1] http://www.w3.org/TR/2006/REC-xml-20060816/#elemdecls
> > [2] http://xerces.apache.org/xerces2-j/faq-xs.html#faq-8
> > [3]
> > http://www.w3.org/Submission/2004/SUBM-xmlschema-api-20040309/xml-
> schema-api.html#ItemPSVI-validationAttempted
> >
> >
> > Michael Glavassevich
> > XML Parser Development
> > IBM Toronto Lab
> > E-mail: mrglavas@(protected)
> > E-mail: mrglavas@(protected)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
> > For additional commands, e-mail: j-dev-help@(protected)
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Validator-
> features-tf2772590.html#a7824915
> Sent from the Xerces - J - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
> For additional commands, e-mail: j-dev-help@(protected)

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@(protected)
E-mail: mrglavas@(protected)


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