Support #5731


Saxon upgrade from 9.x version to 11.4

Added by Urvish Amin 18 days ago. Updated 14 days ago.

Start date:
Due date:
% Done:


Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:


We are trying to upgrade saxon java library from 9.x version to 11.4 version but running lots of xpath related issues. We use it for XSLT transformation. Same xpath works in 9.x version but gives error in 11.4 version. Is there any documentatio/guide available for upgrading from 9.x to 11.4 version? Any configuration settings? We use xslt 2.0.


Actions #1

Updated by Urvish Amin 18 days ago

Following is one of the error we are getting with 11.4 version:

In template rule with match="/" of Int-1.9-TrustActivePayloadBuilderFacade.xsl
Error at char 0 in expression in xsl:variable/@select on line 8 column 68 of Int-CommonFacadeParameters.xsl:
  XPDY0002  The context item for axis step root/descendant::*:REQUEST_HEADER is absent
at variable vv:gg1775669412 on line 40 column 0 of Int-CommonFacadeParameters.xsl:
     invoked by optimizer-generated global variable select="fn:string-join(...)" at file:/tmp/dev/projects/interfaces-service/interfaces-transformer/target/test-classes/UnitTestFacade/facade/Int-CommonFacadeParameters.xsl#40
at template RequestType on line 39 column 37 of Int-CommonFacadeParameters.xsl:
Actions #2

Updated by Urvish Amin 18 days ago

Here is another one:

XPDY0002  The context item for axis step root/descendant::*:MESSAGE is absent
at template mainTemplate on line 20 column 36 of Int-1.9-TrustActivePayloadBuilder.xsl:
     invoked by xsl:call-template
  In template rule with match="/" of Int-1.9-TrustActivePayloadBuilderFacade.xsl
Actions #3

Updated by Michael Kay 18 days ago

When you say "9.x", that covers everything from 9.0 released in 2008 to 9.9 released in 2020, and there was a great deal of change over that time. There are very detailed change logs in the user documentation, but probably far more information than you can wade through. Rather than working out what has changed, it would be best to look at your actual code and see why it is failing. To help you with that, we'll need to look at the code.

Are you running from the command line or from an API, and if so, which API?

What might be happening here is that XSLT 3.0 (and therefore Saxon) introduced the separation between the "global context item" and the "initial match selection". If you run from the command line, the -s option sets both, but on the Xslt30Transformer API they can be set independently of each other. But I'm making wild guesses here because you haven't shown us any code.

Actions #4

Updated by Michael Kay 14 days ago

  • Status changed from New to AwaitingInfo
  • Assignee set to Michael Kay

If you can send us code that we can run to reproduce these errors then it will probably be very easy to tell you what is going wrong. I've marked the post "AwaitingInfo" as we can't do any more without more information from you,

Please register to edit this issue

Also available in: Atom PDF