Sorry, accidentally hit send too soon.. One thing to watch out for: older JREs had a bad habit of including the Apache XML code without changing the package names. This meant that in order to run a newer copy of Xerxes or Xalen you had to either "neuter" the JRE by removing its xml.jar file or make sure the newer Apache code was at the front of the class path by putting it on the bootclasspath. Failing to do so would result in conflicts between the two versions of the code.
The build and test frameworks included with Xerxes and Xalan has been aware of this, and did the right thing. If you are building and testing the code another way, such as in an IDE, you may have to apply those workarounds manually. Newer JREs resolved to this by renaming the Apache packages and advising applications to instantiate them through the javax.* Interfaces, which are derived from the JAXP and TRaX factory layers. That permits compile and test of the Apache-released code and the copy in the JRE to proceed independently, without stepping on each other. Xalan is seriously considering removing the bootclasspath work around from its build and test frameworks, and requiring that those operations be conducted on a JRE which is new enough not to have the class conflicts. I am not sure what the status of Xerxes is in this regard. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________ From: Joseph Kesselman <kesh...@alum.mit.edu> Sent: Sunday, September 22, 2024 11:03:21 AM To: j-dev@xerces.apache.org <j-dev@xerces.apache.org>; mrgla...@apache.org <mrgla...@apache.org>; muk...@apache.org <muk...@apache.org> Cc: j-dev@xerces.apache.org <j-dev@xerces.apache.org> Subject: Re: Xerces Tests One thing to watch out for: older JREs had a bad habit of including the Apache XML code without changing the package names. This meant that in order to run a newer copy of Xerxes or Xalen -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________ From: Svante Schubert <svanteschub...@apache.org> Sent: Sunday, September 22, 2024 10:04:34 AM To: mrgla...@apache.org <mrgla...@apache.org>; muk...@apache.org <muk...@apache.org> Cc: j-dev@xerces.apache.org <j-dev@xerces.apache.org> Subject: Xerces Tests Dear Michael, As the PMC Chair of Xerces, I believe you have insight into the environment in which your project can run the tests successfully without encountering exceptions. Nowadays the latest sources of Xerces can be found on the GitHub branches There are three kinds of tests: 1. The former Xerces tests, run via build.bat test (likely after building with build.bat all), can be found here: a) https://github.com/apache/xerces-j/tree/main/tests or with a single bit of refactoring on the latest branch xml-schema-1.1-dev b) https://github.com/apache/xerces-j/tree/xml-schema-1.1-dev/tests With JDK 8 on W10 the fail with: Provider org.apache.xerces.impl.xs.XMLSchemaValidator could not be instantiated: java.lang.IllegalAccessException: Class org.apache.xerces.dom.ObjectFactory can not access a member of class org.apache.xerces.impl.xs.XMLSchemaValidator with modifiers "protected" 2. The new Xerces Tests from Mukul within https://github.com/apache/xerces-j/tree/xml-schema-1.1-tests/src/org/apache/xerces/tests 3. The W3C XSD conformance tests https://github.com/apache/xerces-j/tree/xml-schema-1.1-tests/w3c_xmlschema11-testsuite There is no runner for the tests, nor a description of where to get them and execute the tests, but there have been tests results: https://www.linkedin.com/pulse/apache-xercesj-w3c-xml-schema-test-suite-reports-mukul-gandhi/ (even if I check out the Xerces-J being used: svn checkout -r 1920842 https://svn.apache.org/repos/asf/xerces/java/trunk/ I got with JDK8 .\build.bat test [java] Tests run: 72, Failures: 7, Errors: 0 It would be particularly helpful if you could provide guidance on running the W3C test suite, especially with respect to the test runner for loading and saving the suite. I am unsure if there is a misconfiguration on my part—whether it be related to the JDK, platform, or other settings—or if Xerces-J has been encountering test failures for some time. Additionally, considering that the W3C XSD 1.1 spec mentions compatibility with XSD 1.0, would it not be beneficial to merge everything into a single branch to avoid data duplication? I trust that, as the PMC Chair, you can provide answers to these questions. Thank you in advance for your assistance. Best regards, Svante
