XSLTGeneral 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 tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developersí questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
Can somebody suggest me a good XSLT processor for MAC version. Till date I've been using TestXSLT for my development processes, but would prefer to use a processor that can triggered from Terminal using shell scripts (I think that is more safe and fast). I am new on MAC though have worked on windows with Xalan processor.
My second question is, which XSLT processor is more safe/better to use from the following:
The reason I am asking this that I've noticed that sometimes while transforming the same XML with same style sheet Sablotron gives errors, while LibXSLT gives the perfect output.
Is it related with the compatibility of processors or something wrong with TestXSLT, as the website from where I've downloaded the TestXSLT also mentions that it is just for testing purposes. Another reason for not using it in regular production floor.
As the author of Saxon I can't really give impartial advice... And I don't know the MAC environment, or TestXSLT. All these processors have a good reputation, though I think LibXSLT is generally preferred over Sablotron these days. If you're getting different behavior it might be a bug, or it might be that the spec allows different behavior, in which case its good to know that your stylesheet is doing something that's processor-dependent. So rather than just abandoning one processor, narrow down what the difference is and investigate it.
Given a choice I would always choose Saxon, the advantage of getting the XSLT to work in Xalan is that that is the standard Java offering and many places are stuck with it, although it doesn't support version 2.0. So it depends somewhat on where you are developing for.