Saxon » Saxon-CE

With the current version when several script elements with language="xslt2.0" are provided, the first one is taken into account and the others are just ignored.

It can be useful, for instance when you have transformations implementing independent sets of features, to provide several script elements, each of them making a reference to a different XSLT transformation (after all, this is even a most common practice in JavaScript).

Note that in JavaScript, it is already possible to create several XSLT20Processor objects and get them running in parallel through their updateHTMLDocument() methods without obvious issues (this is working fine at least for simple examples) and this FR would just be a matter of exposing this ability more declaratively.