Saxon XSLT Processors
<%=ConfigurationManager.AppSettings["SS"]%> has partnered with Saxonica, an industry leading provider of Java-based XSLT and XQuery processing components to offer the most robust XSLT development environment on the planet, featuring full support development and deployment using the Schema-Aware Saxon <%=ConfigurationManager.AppSettings["NEWSAX"]%> XSLT and XQuery processor!
Robust Saxon Feature Support
<%=ConfigurationManager.AppSettings["SS"]%> includes Saxon 6.5.5, Saxon-B <%=ConfigurationManager.AppSettings["NEWSAX"]%> and Saxon-SA <%=ConfigurationManager.AppSettings["NEWSAX"]%> (the final one in <%=ConfigurationManager.AppSettings["SSXE"]%> only). Here's a feature support matrix:
| Feature | Saxon 6.5.5 | Saxon-B <%=ConfigurationManager.AppSettings["NEWSAX"]%> | Saxon-SA <%=ConfigurationManager.AppSettings["NEWSAX"]%> |
|---|---|---|---|
| XSLT 1.0 |  |
|
|
| XSLT 1.1* | |
N/A | N/A |
| Basic XSLT 2.0 | N/A | |
|
| Schema-Aware XSLT 2.0 | N/A | N/A | |
| Debugging | |
|
|
It's only natural that this debugger should lead the way. After all, it was <%=ConfigurationManager.AppSettings["SS"]%> that invented XSLT debugging way back in 2000# with <%=ConfigurationManager.AppSettings["SS"]%> 2.0. |
|||
| Backmapping | |
|
|
| Profiling | |
|
|
| Mapping | |
|
|
| Sense:X for XSLT and XPath | |
|
|
The editor is context-aware, so not only is there syntax coloring, but depending on whether the transform is XSLT 1 or XSLT 2, the language hinting and coloring change. Support is also included for the Saxon-specific extensions that are provided with either Saxon version. |
|||
| Java Extension Functions | |
|
|
This debugger is unique in that it is language- and platform-agnostic. You can embed Saxon in an XML Pipeline, and set breakpoints and examine values at the pipeline level. Then you can step into the XSLT (or XQuery, for that matter), and set breakpoints and examine variables there. And then you can step right into Java extension functions and debug there using the Java IDE! |
|||
| XML Publishing | |
|
|
The XML Report module will let you generate XSLT 1 or 2 code that will in turn create your HTML+CSS and/or XSL-FO/PDF output. |
|||
| XML Pipelines | |
|
|
Any version of Saxon can be used within the XML Pipeline to deploy multi-stage transforms which can freely mix XSLT, XQuery, validation, conditional processing, format conversion and input/output. |
|||
| * | XSLT 1.1 was withdrawn as a standard, but still sometimes you find it in the field. |
| # | Remember that 2000 was waaay back in the last millenium. So this is our second millenium of XSLT debugging expertise. |
| N/A means Not Applicable. | |
Schema-Aware XSLT and Basic XSLT Saxon Included!
In <%=ConfigurationManager.AppSettings["SSXE"]%>, both the Basic and Schema-Aware versions of Saxon are included (for XQuery also). And the same configuration options that are exposed through the Saxon command-line interface are also available through the processor-aware Scenarios dialogs:
Executing and Debugging XSLT Expressions Using Saxon
These ultra-sophisticated XSLT tools, including our award-winning XSLT editor and XSLT debugger, provide seamless integration with the Saxon XSLT engine, enabling you to exactly replicate your development and production environment settings. There is no more of this "profile with our engine, deploy with yours" nonsense. You can write, test, debug and deploy all with the same processor. No proprietary XSLT processor lock-in because of non-standard APIs, either. Saxon supports DOM/SAX/JAXP for XSLT and validation, as does the driving code <%=ConfigurationManager.AppSettings["SS"]%> can generate. So you can reproduce and diagnose bugs with high fidelity, simplifying advanced XSLT troubleshooting.
Saxon <%=ConfigurationManager.AppSettings["NEWSAX"]%> XSLT Has Never Looked More Beautiful
<%=Global.ThumbOf("/images/screenshots/saxon_xslt_processor.gif", 450, "Executing and Debugging XQuery Using the Saxon XML Processor")%>
Need we say more? Try out Saxon-SA with a free evaluation download of <%=ConfigurationManager.AppSettings["SSXE"]%> right now.