Re: Xerces-J 2.12.0 vs. Saxon: XSD 1.1 CTA validation errors

Mukul Gandhi <[email protected]> Wed, 8 Aug 2018 11:37:19 +0530

Newsgroups	gmane.text.xml.xerces-j.user
Message-ID	<CABuuzNMwtGv8e6h+O+jc6CiO52=6xgAh+mLqjJvp-UDaLi57HQ@mail.gmail.com>

On Tue, Aug 7, 2018 at 9:15 PM, ykhabins <[email protected]>
wrote:

> Finally, I narrowed it down...
> There are 2 scenarios:
>
>    1. XSD file is specified inside the XML file via xsi:schemaLocation
>    attribute.
>    The -fx parameter is ignored. And it causes CTAs to fail to pick up
>    the full XPath 2.0
>    2. XSD file is specified via command line parameter *"-a"*.
>    The -fx parameter is taken into the account.
>    CTAs pick up the full XPath 2.0
>
> It is a bug.
>
 I agree. You might report this bug for the jaxp.SourceValidator, at
Xerces-J's Jira site.

also, jaxp.SourceValidator is just a sample. You might try writing a Java
component from scratch using XSD 1.1 support available in Xerces, using
JAXP API for XSD 1.1 validation. That should work I believe, for your
scenario.

-- 
Regards,
Mukul Gandhi