

- OXYGEN XML DEVELOPER DEBUG PARAMETERS HOW TO
- OXYGEN XML DEVELOPER DEBUG PARAMETERS MAC OS X
- OXYGEN XML DEVELOPER DEBUG PARAMETERS FULL
- OXYGEN XML DEVELOPER DEBUG PARAMETERS CODE

We can extend the standard Xerces parser to insert trace calls in xsl:template bodies.

It declares methods like startElement, startCDATA, endCDATA and allows clients to implement custom XML parsers. XMLReader is a Saxon compatible SAX interface. What if we could insert the trace calls dynamically, taking the guesswork out of debugging? The good news is that we can. What is more, XSLTTraceListener can be extended to produce pretty HTML reports. It can be stored, analysed and transformed as XML documents normally can. The good part about the trace output is that it's XML :-). But what are the advantages over using xsl:message? It's even worse, since the output is more verbose. We have managed to combine source and stylesheet information within a single output. I can also complement the trace info by adding user trace calls. tTraceListener(new XSLTTraceListener()) Ī trace is printed to standard output as a well-formed XML document.
OXYGEN XML DEVELOPER DEBUG PARAMETERS CODE
XsltTransformer xsltTransformer = // Initialisation code Today we are interested in net.sf., a standard implementation of TraceListener, which gathers tracing info from XSLT stylesheets.Ĭommand line usage: java -jar saxon9he.jar -T: net.sf. But soon we'll find out how we can benefit from it, too.
OXYGEN XML DEVELOPER DEBUG PARAMETERS MAC OS X
It is also put to good use by XQuery developers, because they don't have such a tool as xsl:message. Oxygen XML Developer 18.1 3.3.1: Installation Options 3.3.2: Windows Installation 3.3.3: Mac OS X Installation 3.3.4: Linux Installation 3.3.5: Windows. It can be used, for example, in performance analysis. Net.sf. is Saxon interface to collect tracing information. But what if I'm dealing with a really complex module with modes and priorities? XSLTTraceListener This method can work if I'm familiar with the code base, which is additionally relatively small. So I estimate which templates might be in use and insert instructions like: And I want to visualise the relation between source nodes and their matching templates.Ī solution which immediately comes to mind is to use xsl:message to collect debug info. I have a source document and a quite complex transform. We'll only need Saxon HE, Xerces and some knowledge of Java.

OXYGEN XML DEVELOPER DEBUG PARAMETERS HOW TO
In this article we'll discuss how to build a personal back-mapping solution for everyday needs. Unfortunately, not all the tools are equally convenient, plus, they cost money, and it often takes time to learn and tune them. So, how can I debug it? Modern XML editors provide excellent XSLT debuggers, and there are back-mapping solutions available on the market. Hmm… What does the xsl:next-match above do? Where does it redirect to? It was me who wrote the code, but I hardly remember what I meant. Have you ever found yourself spending hours trying to track down a transform problem? Especially, when working with a messy or ill-structured XSLT module?
OXYGEN XML DEVELOPER DEBUG PARAMETERS FULL
With 17 major releases across 13 years of operation the annual maintenance offers (averaging around 20% of the full license cost) is cost effective. An optional support and maintenance subscription is available which includes full upgrades, including for major releases during the maintenance period.
