Bug #3095: XPath.evaluate requires platform initialisation - SaxonJS - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #3095

closed

XPath.evaluate requires platform initialisation

Added by John Lumley almost 8 years ago. Updated over 7 years ago.

Status:

Closed

Priority:

Low

Assignee:

John Lumley

Category:

Sprint/Milestone:

Start date:

2017-01-03

Due date:

% Done:

100%

Estimated time:

Applies to JS Branch:

0.9, Trunk

Fix Committed on JS Branch:

1.0

Fixed in JS Release:

Saxon-JS 1.0.0

SEF Generated with:

Platforms:

Company:

Contact person:

Additional contact persons:

Description

Running XPath.evaluate() requires the polyfill functions loaded (such as Math.trunc@) from @BrowserPlatform.initalize()@. Currently this action is not performed by @XPath.evaluate() (but it is by @SaxonJS.transform()@) and requires a deliberate

SaxonJS.getPlatform().initialize({});

beforehand. Preferably this should be triggered from within XPath.evaluate() but only once.

Actions

Copy link

Updated by Debbie Lockett almost 8 years ago

Status changed from New to Resolved
Found in version set to 0.9.1

Moved the initialization (of polyfills and Atomic.init) from within the SaxonJS.transform method to within the main load of Saxon-JS (i.e. initialize method in body of transform.js). Here it has been merged with the code for setting the platform, to form one "initialization phase" consisting of the call of initialize().

This is straightforward for the browser platform.

For the Nashorn platform, this required some reorganisation of code:

Reordering of library loading in RunJSTransform.java, so that JSTestDriver.js is first, and transform.js is last (this order is more comparable to that for the browser platform).
Add platform.initialize method for JSTestDriver, and remove the initialization previously inside the JSTestDriver.transform method.

Actions

Copy link