XSLT and XQuery Debugger

www.altova.com Print this Topic Previous Page Up One Level Next page

Home >  User Guide and Reference > XSLT/XQuery Debugger and Profiler >

XSLT and XQuery Debugger

The XSLT and XQuery Debugger enables you to test and debug XSLT stylesheets and XQuery documents. The XSLT and XQuery Debugger interface presents simultaneous views of the XSLT/XQuery document, the result document, and the source XML document. You can then go step-by-step through the XSLT/XQuery document. The corresponding output is generated step-by-step, and, if a source XML file is displayed, the corresponding position in the XML file is highlighted for each step. At the same time, windows in the interface provide debugging information.

 

The XSLT and XQuery Debugger always opens within a debugging session. Debugging sessions can be of the following types:

 

XSLT 1.0, which uses the built-in Altova XSLT 1.0 engine
XSLT 2.0, which uses the built-in Altova XSLT 2.0 engine
XSLT 3.0, which uses the built-in Altova XSLT 3.0 engine
XQuery 1.0, which uses the built-in Altova XQuery 1.0 engine
XQuery 3.1, which uses the built-in Altova XQuery 3.1 engine

 

Note:XQuery Update Facility 1.0 and XQuery Update Facility 3.0 are currently not supported in XSLT and XQuery Debugger.

 

Which kind of debugging session is opened is determined automatically by the type of document from which the debugging session is opened (hereafter called the active document or active file). XSLT debugging sessions are opened from XSLT files (which version depends on the value of the version attribute of the xsl:stylesheet (or xsl:transform) element in the XSLT stylesheet ("1.0" for XSLT 1.0, "2.0" for XSLT 2.0, and "3.0" for XSLT 3.0)). XQuery debugging sessions are opened from XQuery files in a similar way. If the active file is an XML file, the selection depends on whether you choose to run an XSLT or XQuery file on the XML file; if the former, the selection further depends on whether the stylesheet is an XSLT 1.0, XSLT 2.0, or XSLT 3.0 stylesheet.

 

This information is summarized in the table below.

 

Active File

Associated File

Debugging Session

XSLT 1.0

XML; (required)

XSLT 1.0 (using built-in Altova XSLT 1.0 engine)

XSLT 2.0

XML; (required)

XSLT 2.0 (using built-in Altova XSLT 2.0 engine)

XSLT 3.0

XML or JSON; (required)

XSLT 3.0 (using built-in Altova XSLT 3.0 engine)

XQuery 1.0

XML; (optional)

XQuery 1.0 (using built-in Altova XQuery 1.0 engine)

XQuery 3.1

XML or JSON; (optional)

XQuery 3.1 (using built-in Altova XQuery 3.0 engine)

XML

XSLT 1.0, 2.0, or 3.0, or XQuery 1.0 or 3.1; (required)

XSLT 1.0, 2.0 or 3.0, or XQuery 1.0 or 3.1. XSLT version depends on value of version attribute of xsl:stylesheet (or xsl:transform) element of XSLT stylesheet.

 

For details about the three Altova engines, please see the XSLT and XQuery Engine Information section in the Appendices.

 

Automating XSLT and XQuery tasks with Altova RaptorXML Server 2019

Altova RaptorXML Server contains Altova's XML Validator, XSLT 1.0, 2.0, and 3.0 engines, and XQuery 1.0  and 3.1 engines. It can be used from the command line, via a COM interface, in Java programs, and in .NET applications to validate XML documents, transform XML documents using XSLT stylesheets, and execute XQuery documents.

 

XSLT and XQuery tasks can therefore be automated with the use of Altova RaptorXML Server. For example, you can create a batch file that calls Altova RaptorXML to transform a set of XML documents or to execute a set of XQuery documents. See the RaptorXML Server documentation for details.

 

Altova website: AltovaWebLink XSLT Debugger, XQuery Debugger

 


© 2019 Altova GmbH