Cart
[Home] [By Thread] [By Date] [Recent Entries]
Stylus Studio and oXygen both have good debuggers.
Many XSLT bugs, however, boil down to path expressions that don't select anything. Debuggers will often point you quickly to the path expression that's faulty, but after that it's usually a question of staring at the path until you see what's wrong - unless you invest the effort into writing schema-aware code, in which case there's a prospect that the compiler will be able to tell you when you write impossible paths. Michael Kay Saxonica On 11/06/2010 19:56, Monosij Dutta-Roy wrote: I am new to XSLT. However I have gotten some transforms running. In general my background is Java / Oracle - and with that I am wondering what is a good way to debug XSLT other than printing output.
|
