Project

Profile

Help

Feature #5462

closed

Add "-relocate" command line option for XX compiler (xslt3 package)

Added by Debbie Lockett almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Low
Category:
-
Sprint/Milestone:
-
Start date:
2022-04-28
Due date:
% Done:

100%

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

Description

The -relocate command line option is provided for use when exporting SEFs with SaxonEE, but this option is not currently provided with the SaxonJS xslt3 command line package. It would be useful to add it.

Currently all XX-compiled SEFs are "relocatable" - which means that the static base URI is the deployed location of the SEF, rather than the location of the XSLT stylesheet at compile time. But note that unlike XJ-compiled relocatable SEFs, XX SEFs do still contain base URI information referencing the compile time location - which should be removed.

Actions #1

Updated by Debbie Lockett almost 2 years ago

  • Status changed from New to Resolved
  • Assignee set to Debbie Lockett
  • Fix Committed on JS Branch 2, Trunk added

Updates committed on saxonjs2 and main branches, to implement the -relocate command line option for the XX compiler. The XX compiler has been updated so that it really does produce true relocatable SEFs: i.e. base URI information is now omitted for relocatable SEFs.

As for exporting to SEF with the SaxonJ command line, the default for -relocate is false. Note that previously all XX SEFs were labelled as "relocatable", though this wasn't entirely true, and they weren't necessarily treated as such. So it is possible that there may be some subtle changes in behaviour using new XX SEFs where static base URI is concerned; to bring it into line with the (correct) expected behaviour for relocatable and non-relocatable SEFs.

Relevant unit tests have been updated.

Actions #2

Updated by Debbie Lockett almost 2 years ago

Documentation updates also committed.

Actions #3

Updated by Debbie Lockett almost 2 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in JS Release set to SaxonJS 2.4

Bug fix applied in the SaxonJS 2.4 maintenance release.

Please register to edit this issue

Also available in: Atom PDF Tracking page