Tools for debugging xslt

Question

I have a Java servlet which generates XML, translates it with an XSLT stylesheet, and then displays the resulting HTML. This is the first time I've worked with XSLT. What's a good way to debug XSLT? I have (or can get) some sample XML files to apply the transform too. But I'm not really even sure of the syntax so something that would give me syntax warnings would be great.

Gilbertson

There is a detailed comment on anothur similar question https://mcmap.net/q/408659/-debugging-xslt-in-chrome-closed – Dreadnought

Answer 1

Xalan should give you useful errors when you try to use an invalid XSLT. If you want something more powerful, one option for debugging XSLT is Oxygen XML Editor. It is integrated with Xalan and Saxon transform engines. Its debugging mode allows you to set breakpoints, watch variables, and provides other such basic debugging functionality. It may be overkill for you want, but it's very good.

Knavish

Answer 2

If you want to do "printf-style" debugging and don't want to litter your output with debugging data, use the <xsl:message> tag to generate debugging output while processing the stylesheet. With the terminate="yes" attribute you can even halt the processing of the stylesheet.

Rhotacism

A) Using commandline xmllint mytransform.xsl as a basic syntax checker is helpful to catch mismatched braces etc. B) Also running a commandline processor in verbose mode can be really helpful esp. when you don't know why xslt is choking on your code. xsltproc -v mytransform.xsl input.xml &>log.txt dumps a LOT of info from the xsltprocessor. Filter out the noise by using search with vim or grep for your debug messages like "DEBUG: Start of my code" or useful string patterns like 'applying template'. – Mihalco

Answer 3

I once had to write and debug some complex XSLT documents. At the time I used debugged "printf-style" by outputting a lot of intermediate values. I later found out that there is a much easier way to do this - Altova XMLSpy. It allows you to single-step through the style-application process, watch intermediate output, etc. etc.

VS8 also has XSLT debugging support. See here: http://msdn.microsoft.com/en-us/library/ms255605(VS.80).aspx

I should also mention that both XMLSpy and VS8 have syntax highlighting as well. If you specify a XSD in your XML, VS8 even gives you intellisense!

Golub

Unfortunately, I can't justify the cost to my boss for the limited use I'd get, for now. If this turns into a longer term project, I may be able to get one or the other. – Gilbertson

Just download the Express edition of Visual Studio then. It's free. – Twophase

A great post about Visual Studio's XSLT debug support here: codeproject.com/Articles/41992/… – Ventricular

On a separate issie, I'm having a performance related issue. I need to use the printf style logging to simply insert timestamps before and after critical sections of code to find which XSLT sections are consuming too much time. Any links to C# window's log write from XSLT? – Revue

Answer 4

PHPStorm and the other IntelliJ IDEs (commercial) support debugging XSLT. You can step through the document and see the output being generated step by step.

Medovich

Answer 5

I work with XSLT nearly every day, and have for six or seven years.

I've found that "printf-style" debugging of XSLT is so effective that I've never derived a benefit from using any other debugging mechanism (and I've tried XMLSpy and Visual Studio). It does sometimes happen that I want to be able to inspect the value of a variable and building logic that outputs it is a hassle. But that's pretty rare.

It may be that having a debugger would have made learning XSLT easier. (Anything would have.)

Hallsy

I think an example would be helpful. – Teno

Answer 6

when learning, a syntax highlighting editor is usually enough for me (of course with the ref doc open on another window.

Kate is a great editor for XML and XSLT.

Manisa

A syntax highlighter is helpful. I'm using VI on my server right now because I'm not done setting up my dev environment. But what I really want is to be able to run the xml and xslt through a processor and get error messages or whatever without having to run the whole servlet process. – Gilbertson

try a command-line xslt processor; i use xalan, but anyone would do. I'm sure vi can run it and won't be surpriesed if it could even parse the error outputs like it does with compilers – Manisa

Oh, you absolutely want to be executing your transforms and viewing their output in your IDE. I don't think a debugger's very important, but that's essential. – Hallsy

Answer 7

Xselerator is s great XSL debugging tool that will:

• Let you step through your XSLT dom
• Create watch statements
• Evaluate XPath statements against you XML DOM
• IDE with Intellisense

I've used this for years and it is a great tool.

Tombstone

Answer 8

An answer specifically for debugging XSLT 3.0 with <xsl:message>:

XSLT 3.0 has a new serialize() function that can help when used inside an xsl:message instruction.

However, for the new array and map types you need to use the adaptive serialisation method instead of default XML serialization:

<xsl:message select="serialize($n, map{'method':'adaptive'})"/>

The current drawback with serialize though is that it does not format the output.

A small xpath-result-serializer XSLT project provides ext:print() and ext:println() functions as an alternative to serialize(). There format (and optionally colorise) the XSLT output.

The output text uses an abbreviated notation for maps/array optimised for the human reader rather than a parser. For XML nodes with context, the XPath location is output alongside any text or attribute values.

Vesuvian

Answer 9

Microsoft Visual Studio is also a great tool for xslt debugger. But you must install the visual studio component, office development component.

Jessi

Install the visual studio component , office development component – Jessi

You can edit the answer. Though I don't see that this adds anything to this ten-year-old question, that hasn't been mentioned yet. – Wanhsien