Dick Deneer <[EMAIL PROTECTED]> wrote on 12/21/2006
03:47:08 PM:
> My conclusion is, reading your answer, that there is no way at this
> moment to match the error against a specfic node,
Right. There's no way that you can do this with Xerces today.
> I hope there will be support for the "curr
My conclusion is, reading your answer, that there is no way at this
moment to match the error against a specfic node,
I hope there will be support for the "current-element-node" in the
XMLGrammarPreparser in one of the coming releases.
Thanks
Dick Deneer
Op 21-dec-2006, om 21:27 heeft Micha
Hi Dick,
The "current-element-node" property was only implemented for validation of
instance documents. There's no support for it in the schema loader.
As for PSVI... It's the result of validating an instance [1] not checking
constraints [2] on the schema itself. It isn't relevant to SchemaFact
Michael,
I first tried the xerces way by using the XMLGrammarPreparser and a
DOMIputsource.
But how can I get the domNode that causes the error.
XMLGrammarPreparser.getProperty
(XMLGrammarDescription.XML_SCHEMA,"http://apache.org/xml/properties/
dom/current-element-node") is not accepted.
An
Dick Deneer <[EMAIL PROTECTED]> wrote on 12/18/2006
04:45:53 PM:
> I am using the DOMNormalizer to validatie instance document against
> DTD or XSD.
> I noticed that this even works when the instance document itself is
> an xsd. You can give http://www.w3.org/2001/XMLSchema.xsd as the
> sch
