Project

Profile

Help

Bug #4544

Packages listed in -lib on Transform command line must be source XSLT, not SEF files

Added by Michael Kay about 1 year ago. Updated 8 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XSLT 3.0 packages
Sprint/Milestone:
-
Start date:
2020-05-05
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
10, 9.9
Fix Committed on Branch:
10, 9.9
Fixed in Maintenance Release:

Description

I've been trying to run

net.sf.saxon.Transform -lib:package.sef

and it fails saying XTSE0150 The supplied file does not appear to be a stylesheet.

The spec for the command line says the file can be either source XSLT or a SEF file, and we try generally to allow a SEF file anywhere source XSLT is allowed.

History

#1 Updated by Michael Kay about 1 year ago

  • Status changed from New to Resolved
  • Applies to branch 10, 9.9 added
  • Fix Committed on Branch 10, 9.9 added

Fixed on the 9.9 and 10.0 branches. PackageInspector was already designed to handle either source XSLT or SEF; but it was leaving the location in both cases in PackageDetails.sourceLocation rather than PackageDetails.exportLocation, and PackageLibrary.obtainLoadedPackage() was assuming that sourceLocation contained XSLT source.

At the same time I added some version-checking diagnostics: 9.9 checks that the SEF file isn't produced by 10.0+, and vice versa.

#2 Updated by O'Neil Delpratt about 1 year ago

  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 10.1 added

Bug fix committed in the Saxon 10.1 maintenance release.

#3 Updated by O'Neil Delpratt 8 months ago

  • Status changed from Resolved to Closed
  • Fixed in Maintenance Release 10.2, 9.9.1.8 added
  • Fixed in Maintenance Release deleted (10.1)

Bug fix applied on the Saxon 9.9.1.8 maintenance release.

Please register to edit this issue

Also available in: Atom PDF