Skip to content

Extract Saxon version into property and remove XPath limit workarounds#1199

Draft
Copilot wants to merge 3 commits intomasterfrom
copilot/improve-xpath-limit-process
Draft

Extract Saxon version into property and remove XPath limit workarounds#1199
Copilot wants to merge 3 commits intomasterfrom
copilot/improve-xpath-limit-process

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 1, 2026

  • Extract Saxon version into a saxon.version property in root pom.xml
  • Reference ${saxon.version} in quickfixj-codegenerator/pom.xml (was hardcoded 12.9)
  • Add Saxon-HE as a dependency of xml-maven-plugin in root pom.xml so XSLT 2.0 stylesheets are processed by Saxon instead of the JDK's Xalan (which hits XPath operation count limits)
  • Refactor quickfixj-base/src/main/xsl/extractRequiredFields.xsl — replace long chain of or @id='...' predicates with compact XSLT 2.0 sequence syntax @id = ('a','b','c',...)
  • Refactor quickfixj-messages/quickfixj-messages-all/src/main/xsl/minimiseOrchestra.xsl — same XPath sequence refactoring
  • Refactor quickfixj-orchestration/src/main/xsl/extractSessionLayer.xsl — same XPath sequence refactoring
  • Remove -Djdk.xml.xpathExprGrpLimit=500 -Djdk.xml.xpathExprOpLimit=500 from .mvn/jvm.config
  • Remove the same flags from the documented build command in .junie/guidelines.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Get rid of XPath limit configuration

2 participants