Project

Profile

Help

Bug #5679

closed

SaxonJS and the documentPool

Added by Norm Tovey-Walsh 24 days ago. Updated 4 days ago.

Status:
Resolved
Priority:
Low
Category:
-
Sprint/Milestone:
-
Start date:
2022-09-06
Due date:
% Done:

0%

Estimated time:
Applies to JS Branch:
Fix Committed on JS Branch:
Fixed in JS Release:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

This bug tracks an issue raised initially on the XML.com Slack. (This gives it a bug number for my local test case, more than anything else.)

Actions #1

Updated by Norm Tovey-Walsh 24 days ago

Everytime you run a transformation, any event handlers in the stylesheet get instantiated. If you run the same stylesheet more than once, then they get instantiated more than once.

The behavior seen with the documentPool is red herring. The first transformation, the one with the document pool established on it, always succeeds. The apparent failure arises because event handlers instantiated in subsequent uses of that stylesheet, without establishing a document pool, also run and they fail.

It's not clear that there's anything unexpected going on here.

Actions #2

Updated by Norm Tovey-Walsh 4 days ago

  • Status changed from New to Resolved

Added a test case to demonstrate that setting the nonInteractive option to true prevents the event handlers from being re-applied.

(No code changes were required to resolve this issue.)

Please register to edit this issue

Also available in: Atom PDF Tracking page