Bug #2687: -xsl with http location stopped working - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #2687

closed

-xsl with http location stopped working

Added by Alexander Henket over 8 years ago. Updated over 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Command Line

Sprint/Milestone:

9.7.0.4

Start date:

2016-03-24

Due date:

% Done:

Estimated time:

Legacy ID:

Applies to branch:

9.7, trunk

Fix Committed on Branch:

9.7, trunk

Fixed in Maintenance Release:

Platforms:

Description

Hi, I use saxonpe command line. When I use SaxonPE 9.5 I can use this command:

$ java -jar ~/Development/lib/SaxonPE9-5-1-10J/saxon9pe.jar -xsl:http://art-decor.org/ADAR/rv/DECOR2schematron.xsl -s:input.xml

And get the desired output, but using SaxonPE 9.7.0.4 I get:

$ java -jar ~/Development/lib/SaxonPE9-7-0-4J/saxon9pe.jar -xsl:http://art-decor.org/ADAR/rv/DECOR2schematron.xsl -s:input.xml

    ....
    Stylesheet file http does not exist

Is that intended regression?

Actions

Copy link

Updated by Michael Kay over 8 years ago

Thanks for reporting it. It's an unintended consequence of a new feature. In 9.7 the -xsl option allows a list of stylesheet packages to be supplied, separated by :" or ";" depending on the conventions of the operating system. So the in the URI (on a unix-like platform) is being misinterpreted as a separator between two filenames.

We'll have to think what to do about this.

Actions

Copy link

Updated by Alexander Henket over 8 years ago

Thanks. 9.5/9.6 works fine so I'm in no immediate trouble.

Actions

Copy link

Updated by Michael Kay over 8 years ago

Status changed from New to In Progress
Fix Committed on Branch 9.7 added

I have produced a patch such that if the -u option is present, or if the value of the -xsl option starts with a URL scheme such as file:, http:, or https:, then the option is treated as a single filename/URL rather than as a colon-separated sequence of names.

This isn't entirely satisfactory in the long term but it's the best I can come up with to retain backwards compatibility.

Leaving the bug open so we can document the change and consider future options for a next release.

Actions

Copy link