Saxon » SaxonJS

I have resolved this particular test case by introducing logic to allocate a random unique ID to each key definition on initialisation of the transformation.

This also solves another problem, namely that indexes created for a source document during one transformation might be reused by another transformation even though stylesheet parameters used within the key definition are different, meaning that old index is no longer applicable.

However, I have done it by writing additional attributes to the SEF DOM, which is incorrect, because two concurrent transformations might be using the same SEF DOM.

The current patch also causes regression to one test case in the "key" test set, which needs investigation.

I have now amended the solution so the dynamically-allocated unique ID of an index is held locally (in context data) rather than by modifying the SEF DOM. Committing this solution.