oXygen and Stylus Studio are both pretty good at keeping up to date with Saxon releases - they have both been working on integrating Saxon 9.4, I'm not sure of the exact release status but if one of them is ahead one week, the other will soon leapfrog it. Both will support XSLT 3.0 features to the extent that Saxon supports them. Both include the ability to use Saxon-EE features within the IDE.  Both have their own debugging capability built on top of the low-level debugging APIs in the Saxon product.

Note that XSLT 3.0 has only had one working draft so far, so it's still very much a moveable feast.

EditIX ships only with the open-source version of Saxon, though I imagine it will work with Saxon-PE and Saxon-EE if you buy your own license.

Michael Kay

On 03/04/2012 13:42, David Rudel wrote:
Hi all,
I'm trying to find the best IDE to use for XSLT development, with particular interest in support/integration for the XSLT3/XPATH3 capabilities found in Saxon's professional processors and the saxon extensions.

Michael has indicated that both oXygen and Stylus Studios are partners with Saxonica, so I am only considering those two.

It appears that Stylus Studios does not ship with a professional version of Saxon, but I have a PE license, so the question there is how easy it is to incorporate that transformer into their IDE.
oXygen appears to ship with Saxon9EE!!, but I believe it is an earlier EE [maybe 9.3EE] and to be honest I would prefer in general using my personal PE license that I know I can upgrade as new versions become available and more XSLT3/XPath3 is incorporated into Saxon.

oXygen appears to use Saxon's own debugging tools, which is a plus, I presume.

The balance of the above suggests oXygen offers closer support for Saxon, but then I notice that there is not a single reference to XSLT3 on their entire website. Stylus Studios, OTOH, advertises on their front page that their newest enterprise edition has XSLT3 support [but one cannot tell whether the same is true of their not-quite-as-expensive Professional Edition.]

Note, the above remarks/concerns might seem rather queer, as one would presume that things like saxon extension support and use of XSLT3 capabilities would come automatic with the transformer itself. However, I have not found this to be the case when using EditiX:

1. EditiX cannot use saxon extnesions in its native IDE debugger.
2. EditiX cannot even run XSLT3-enabled stylesheets. [If you set "xsl:stylesheet version=3.0" in the top element, no transformation occurs at all.] In order to use XSLT3 capabilities, one has to create an external tool that just calls the transformer from the command line, which is fine for doing the transformation but obviously means that the IDE is useless of authoring purposes.

Obviously, I will be downloading and trying out the evaluation versions to answer some of these questions, but I'd be interested in other people's experiences with these IDEs and their compatibility with SAXON and XSLT3.



"A false conclusion, once arrived at and widely accepted is not dislodged easily, and the less it is understood, the more tenaciously it is held." - Cantor's Law of Preservation of Ignorance.

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.

saxon-help mailing list archived at http://saxon.markmail.org/