Page 1 of 1

Version of xercesImpl in Oxygen

Posted: Mon Jun 02, 2014 5:34 pm
by hutchkintoot
Hi

We have developed an xsd-schema that validates instances fine in Oxygen 15 and 16. However when we use the schema in our application (with xerces 2.11.0Beta, downloaded from xerces binary releases) the validation fails on certain identity-constraints on the same instances.

After looking att the xercesImpl provided in Oxygen i can see that the version number is the same (2.11.0Beta) but the size of the jars differs when compared with the one downloaded from xerces site.

Is the xerces-distribution that you use i Oxygen available for download somewhere? (we really need the beta version since we are using xsd version 1.1 for some of our schemas)

Regards,
Johan Mörén

Re: Version of xercesImpl in Oxygen

Posted: Tue Jun 03, 2014 1:32 pm
by hutchkintoot
I found the root of the problem when regarding the failing constraints. When declaring keys and keyrefs it seems like the official release of Xerces 2.11.0Beta will not resolve the keyref if the data type of the key and keyref are different or undeclared.

However the version of Xerces and Saxon-EE in Oxygen 15 and 16 manages to resolve the references.

I'm however still interested in getting hold of the Xerces distribution that is bundled with Oxygen. And if that is not possible maybe you should point out that the version of Xerces that you use is a patched version. Today if i check library versions in the about dialog, the version of Xerces is printed as 2.11.0, but in fact it is 2.11.0Beta (with support for xsd 1.1).

Regards,
Johan Mörén

Re: Version of xercesImpl in Oxygen

Posted: Tue Jun 03, 2014 2:47 pm
by adrian
Hello,

Oxygen uses a build of Xerces from the XML Schema 1.1 development branch:
https://svn.apache.org/repos/asf/xerces ... ma-1.1-dev
You are welcome to use the xercesImpl.jar from Oxygen. Or you can check out the source code from the Apache SVN repository and re-build the jar yourself.

Note that in addition to this, Oxygen also patches a few known issues in its internal code, so there may still be some differences in behavior in some limited scenarios.

Regards,
Adrian