[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xsl] Upgrading to XSLT 2.0
Subject: Re: [xsl] Upgrading to XSLT 2.0 From: David Carlisle <davidc@xxxxxxxxx> Date: Wed, 25 Oct 2006 01:39:06 +0100 |
> My question: How easy/painful is this processor/language upgrade? depends a bit on your existing 1.0 stylesheets. XSLT2's backward compatibility mode ended up being quite good really (a lot better than it appeared it was going to be initially) so if you have a pure xslt 1 stylesheet, chances are that it will run as-is if you don't change it at all and run on an xslt2 system. If your stylesheets use xslt 1 extensions then since you are changing processor the extension namespace may not be supported in the new processor, so you may have to change the code slightly, often there is a built in xslt2 function (eg replace saxon6:node-set() by nothing, or saxon6:output by xsl:result-document) Note that differences in supported extensions is a problem due mainly to changing processors rather than changing between xslt1 and xslt2 (if you switched between saxon6 and xalan, you'd have to make simlar changes, changing saxon6:output to xalan:redirect etc) > Please forgive if this question seems a bit naove Not at all naive, and it's a question thats going to get asked a lot in the coming months, as (one hopes) they'll finally finish the xquery/xslt spec process and xslt2 will become an offical REC. So many people holding off using XSLT2 while it is still offically a draft spec will start to seriously consider switching... David
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Upgrading to XSLT 2.0, Lorand, William | Thread | RE: [xsl] Upgrading to XSLT 2.0, Michael Kay |
Re: [xsl] recursive lists displayin, Joelle Tegwen | Date | Re: [xsl] getting type information , Dimitre Novatchev |
Month |
Keywords