Bug #2261: With bytecode on, apply-imports fails to set current component - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #2261

closed

With bytecode on, apply-imports fails to set current component

Added by Michael Kay about 10 years ago. Updated about 9 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Michael Kay

Category:

Byte code generation

Sprint/Milestone:

9.6.0.4

Start date:

2014-12-15

Due date:

% Done:

100%

Estimated time:

Legacy ID:

Applies to branch:

9.6

Fix Committed on Branch:

9.6

Fixed in Maintenance Release:

9.6.0.4

Platforms:

Description

With bytecode generation enabled in Saxon-EE, the xsl:apply-imports instruction fails to make the invoked template the current component in the context, which means that calls to other global components (templates, functions, global variables) from the invoked template may fail to bind correctly. The symptom will often be something like

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0

at java.util.ArrayList.RangeCheck(ArrayList.java:547)

at java.util.ArrayList.get(ArrayList.java:322)

at net.sf.saxon.expr.XPathContextMajor.getTargetComponent(XPathContextMajor.java:778)

at net.sf.saxon.expr.instruct.CallTemplate.process(CallTemplate.java:331)

In the particular instance, the failing stylesheet is the W3C stylesheet used for building the XDM specification,

Actions

Copy link

Updated by Michael Kay about 10 years ago

Status changed from New to Resolved

A patch has been added which causes apply-imports and next-match to generate code that sets the current component in the context. Applied to 9.6 and 9.7; tested (for apply-imports only, but the code is the same) with the W3C build scripts.

Actions

Copy link