Wrox Programmer Forums
Go Back   Wrox Programmer Forums > XML > XSLT
|
XSLT General questions and answers about XSLT. For issues strictly specific to the book XSLT 1.1 Programmers Reference, please post to that forum instead.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the XSLT section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old March 23rd, 2005, 02:50 PM
Registered User
 
Join Date: Mar 2005
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default beginner xslt processor question

I'm looking for some information to help me select an XSLT processing tool, particularly between Saxon and Xalan. One tool that I'll be implementing soon uses Xalan, but I've used Saxon and some Saxon extensions in the past and found those useful. I know there are some biases within this forum:), but there may be extenuating circumstances in my case.

Are there typically complementary extensions for Saxon and Xalan? Are there other factors that should be considered other than the availability of extensions? Are Saxon and Xalan completely interchangeable if I'm able to stay away from extensions?

Any advice would be appreciated.

 
Old March 23rd, 2005, 03:06 PM
mhkay's Avatar
Wrox Author
 
Join Date: Apr 2004
Posts: 4,962
Thanks: 0
Thanked 292 Times in 287 Posts
Default

You need to consider whether you want to use XSLT 2.0. For doing anything but the simplest transformations, features in XSLT 2.0 make your life vastly easier (for example, grouping and regular expression processing). XSLT 2.0 is becoming very stable but it's not yet a firm recommendation. On the other hand, using XSLT 2.0 features is much "safer" than using any vendor's extensions to XSLT 1.0. If you decide to run with XSLT 2.0, then Saxon 8 is really only your only realistic choice at the moment. (XML Spy has support, but it's very early). If you decide to stick with XSLT 1.0, then you have a wide choice of mature products and there's not much to choose between the good ones. In fact, Xalan and Saxon 6 are very interchangeable and many people don't actually know which one they are using. It's therefore not a big decision, because you can change your mind at any time.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference
 
Old March 24th, 2005, 09:01 AM
Registered User
 
Join Date: Mar 2005
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks for highlighting XSLT 2. I wasn't aware of the significance of the new feature set. I'll take a closer look at that.

When you say
Quote:
quote:Originally posted by mhkay Xalan and Saxon 6 are very interchangeable and many people don't actually know which one they are using. It's therefore not a big decision, because you can change your mind at any time.
does that assume there are no extensions involved? If I'm using, for example, saxon:assign, is there an identical xalan:assign or will the saxon extension work with xalan? I was under the (perhaps false) impression that extensions are processor-specific. Is the same true for third party extensions? I haven't considered those at this time.

Thanks for the help.

 
Old March 24th, 2005, 09:41 AM
mhkay's Avatar
Wrox Author
 
Join Date: Apr 2004
Posts: 4,962
Thanks: 0
Thanked 292 Times in 287 Posts
Default

There are certainly extensions in each of the processors. But many of the most useful ones are available in the EXSLT library, which is widely supported across XSLT 1.0 processors (see www.exslt.org).

saxon:assign won't work with Xalan - but I wouldn't advise using it with Saxon either. It's one of those things like disable-output-escaping that should only be used as a last resort. Unfortunately this isn't always realised by beginners, who tend not to realise how much you can achieve in XSLT - even XSLT 1.0 - without touching extensions.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference





Similar Threads
Thread Thread Starter Forum Replies Last Post
xslt beginner question cfflexguy XSLT 4 October 16th, 2007 09:11 AM
XSLT processor for Mac Pankaj C XSLT 3 September 26th, 2007 08:36 AM
Which XSLT processor? li72 XSLT 1 August 16th, 2007 11:18 AM
Regarding the XSLT Processor sunrain XSLT 5 December 3rd, 2006 03:01 AM
changing xslt processor in FOP Tschuri XSLT 0 May 13th, 2005 07:08 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.