A number of Saxon extension functions have been dropped between Saxon 6.x
and Saxon 8.x: this isn't affected by running in backwards compatibility
mode, they are simply not present in the code. In the cases you cite, there
is a standard XSLT 2.0 facility that replaces the Saxon extension - it's
often not an exact match for the semantics, but usually pretty close.
Generally Saxon maintained support for the old syntax for a couple of
releases after introducing the new, but of course that doesn't help you if
you haven't kept up with all the interim releases.
So I'm afraid you're going to have to convert these constructs over.
Backwards compatibility mode in Saxon only affects the things the spec says
it affects. It doesn't affect anything that's implementation defined,
including extension functions.
> -----Original Message-----
> From: saxon-help-bounces@...
> [mailto:saxon-help-bounces@...] On Behalf
> Of Randall J. Parr
> Sent: 13 October 2007 22:11
> To: saxon-help@...
> Subject: [saxon] XSLT 2.0 backwards compatibility mode
> I have a fairly large set of stylesheets which we use to
> transform large XML files (60M) into web-site / store pages,
> printed catalogs, etc. I have several "stacks" of these
> stylesheets each of which builds from a common base with the
> higher layers extending/overriding the base layer as required
> to output a particular target markup/media.
> These stylesheets are currently written in XSLT 1.0 using a
> few Saxon extensions (group, item, range, distinct) and run
> using Saxon 6.5.5.
> I would like to migrate these stylesheets to XSLT 2.0. My
> plan was to first switch to running the XSLT 1.0 stylesheets
> using Saxon 8.x and correcting those, supposedly few, things
> not handled by "backwards compatibility" mode. Then I would
> convert the stylesheets of one "stack" at a time to version
> XSLT 2.0. Then I would begin refactoring the stylesheets
> leveraging XSLT 2.0 to implement improvements.
> It appears, however, that this is not a viable plan because Saxon 8.x
> (8.9 currently) does not appear to recognize Saxon extensions
> in "backwards compatibility" mode. At least not saxon:group.
> Before I abandon my plan I would like to confirm if it is
> true Saxon XSLT 2.0 "backwards compatibility" mode is NOT
> backwards compatible with Saxon extensions (or if I have not
> configured/run things correctly).
> Are any Saxon extensions supported/recognized in "backwards
> compatibility" mode?
> I would also like to confirm if it is true that all
> stylesheets in a "stack" would have to be converted to
> version 2.0. That is, a version 2.0 stylesheet can not
> include/import a version 1.0 stylesheet. It seems obvious
> but I want to confirm that.
> Temporal Arts
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and
> a browser.
> Download your FREE copy of Splunk now >>
> http://get.splunk.com/ _______________________________________________
> saxon-help mailing list