SAP Integration Suite uses Saxon EE 9.9 and hence allows one to run XSLT 3.0. We would like modularise our code by making use of

Looking at the available information in Saxonica it reports that a package name has to be registered in the EE Config file within xsltPackages/package. However I believe since SAP Integration Suite is an iPaaS solution then we will not have access to put our package names into the EE config file. Are there any other ways for a Stylesheet to find a package? Currently we are able import other Stylesheets when they exist in the same uri location as the already running Stylesheet. It would be great if would could achieve the same for Packages too? Otherwise we would be forced to store all our UTIL functions in a stylesheet as opposed to a package

Looking at the available information in Saxonica it reports that a package name has to be registered in the EE Config file within xsltPackages/package. However I believe since SAP Integration Suite is an iPaaS solution then we will not have access to put our package names into the EE config file. Are there any other ways for a Stylesheet to find a package? Currently we are able import other Stylesheets when they exist in the same uri location as the already running Stylesheet. It would be great if would could achieve the same for Packages too? Otherwise we would be forced to store all our UTIL functions in a stylesheet as opposed to a package

• saxon
• xslt-3.0

Share Improve this question Follow edited Jan 31 at 15:16 Martin Honnen 168k66 gold badges9898 silver badges122122 bronze badges asked Jan 30 at 17:16 AlexAlex 2955 bronze badges 1

• I have added the tag for saxon. Consider to add a tag for that SAP Integration Suite if there is one. – Martin Honnen Commented Jan 31 at 15:17

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

There are other mechanisms for locating packages if you have access to the command line or to the Java API. I don't think there is any way of doing it if you only have access to the XSLT code.