Hi Martin,

On Mon, Feb 16, 2026 at 12:46b/AM Martin Honnen martin.honnen@xxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

>
> As you seem to have implemented xsl:package support, it would be nice to
> know what the status of that is (are packages compiled to one
> executable?)


With Apache Xalan, an XSL xsl:package instruction within one file, is
converted to compiled Templates object, via
method TransformerFactory.newTemplates(..) which is further used with
TransformerImpl.transform(..) method to produce an XSL package's result
output.

An xsl:package may also contain, an XSL instruction xsl:use-package
name="uri", from whose 'uri' (that is resolved with an XSL containing
package's absolute uri) another Templates object is constructed and XSL
components contained within it, are used within the containing XSL package.

Saxon XSL transformer, unlike Xalan, specifies with its command line for
e.g, -lib:package2.xsl to use with xsl:use-package instruction.


> how to use it (any new command line parameter to provide
> packages?).


This requires only, specifying correct xsl:use-package instruction with a
valid 'name' linking to a reachable uri, within an XSL containing package.


> Is there any mapping of package names to package locations?



> Or is the name just serving as the location
>

Yes that's correct.


--
Regards,
Mukul Gandhi