Solved

Where does the <xsl:message...> display in XMLspy?

Posted on 2007-04-02
1
520 Views
Last Modified: 2013-11-18
Hi,
    I'm using XMLspy tool. When I try to use <xsl:message...> tag I couldn't see any ouput in the output file, as I read this tag would send the output to the screen and not to the outputfile.Could any one tell me how to check for the screen where this tag would display in XMLspy?

Thanks
0
Comment
Question by:jdharsha
1 Comment
 
LVL 10

Accepted Solution

by:
BobSiemens earned 50 total points
Comment Utility
     http://www.altova.com/products/xmlspy/xslt_debugger.html



  ProductsXMLSpyXSLT/XPath/XQueryXSLT Debugger
XMLSpy XSLT Debugger

Altova XMLSpy® 2007 includes a powerful XSLT 1.0/2.0 debugger for troubleshooting and perfecting XSLT 1.0 and 2.0 stylesheets.

Testing and perfecting XSLT stylesheets can be a complicated, time-consuming process. With the XMLSpy® 2007 XSLT debugger, you can step through and debug even the most intricate stylesheets quickly and easily.

Altova XMLSpy® 2007 includes a complete implementation of the powerful new XSLT 2.0 and XPath 2.0 specifications, and the XSLT debugger allows you to debug both XSLT 1.0 and 2.0 stylesheets. To learn more about significant technical benefits of XSLT 2.0 and XPath 2.0, visit our XSLT/XPath 2.0 page.
XSLT Debugger

The Altova XMLSpy® 2007 XSLT debugger includes a three-panel interface that displays the XML document, the associated XSLT 1.0 or 2.0 stylesheet, and the output document as it is being built in real-time. Below the three panels, Context and Callstack information windows include multiple tabs that supply all the necessary debugging information.



XSLT Debugger

Demo of building XSLT debugger View a Flash demo of the XMLSpy XSLT debugger now

Depending on the complexity of your XSLT stylesheet and your personal preferences, you can debug XML and XSLT files in Advanced Text View or Grid View, and view the dynamic output in Advanced Text, Grid, and Browser View, switching between the different views as required.

Debugging XSLT Stylesheets

You can start the XSLT debugger at any time when working with an XML or XSLT 1.0/2.0 file. If a permanent XML / XSLT file designation has not been specified, XMLSpy® 2007 will prompt you to select the associated file.

The XML and XSLT files are opened side-by-side next to the output panel, which displays the output file defined by the XSLT stylesheet.

The XSLT debugger allows you to move through the XSLT transformation step-by-step, and you can step into, step out, and step over nodes. The debugger highlights the current XSLT instruction in the XSLT stylesheet and the current node in the XML file, and produces output for each step, which is highlighted in the output pane. The ability to see the specific XML data node, the XSLT processing instruction, and the produced output at the same time provides you with an immediate visual understanding of the way that your XSLT stylesheet is rendering the XML data.
Breakpoints and Tracepoints

When debugging complex XSLT 1.0 or 2.0 stylesheets, it is useful to be able to understand exactly what output is produced by each instruction. In the XSLT debugger, you can define breakpoints in the XML and XSLT files, and tracepoints in the XSLT document.

Breakpoints halt the debugger when a particular node is accessed by an XSLT instruction, allowing you to view the output to that particular point in the transformation. Using the XMLSpy® 2007 XSLT debugger, you’re not restricted to line-by-line breakpoints – you can set breakpoints on any number of individual nodes, attributes, and elements. The ability to set breakpoints on nodes in the XML data file provides you with the ability to halt the debugger whenever that particular node is accessed by any XSLT instruction, e.g., during the execution of an xsl:for-each loop.

When you click the Start Debugger/Go icon, the XSLT processor stops at the first breakpoint and displays all data relevant to the node in the debugger info windows.



XSLT debugger breakpoints

In contrast to breakpoints, tracepoints do not halt the debugger. When a tracepoint is hit during an XSLT debugging session, the instruction is executed, and information is written to the Trace window. Once the transformation is complete, the trace window displays the list of tracepoints as well as the output produced by each. This allows you to view exactly how each XSLT instruction is executed.



XSLT debugger tracepoints

You can also set an XPath for a tracepoint. In this case, the result of the XPath statement is displayed in the trace window.

You can insert/remove and enable/disable breakpoints and tracepoints using the XSLT debugger toolbar, keyboard shortcuts, or via a context-sensitive right-click menu.



setting breakpoints and tracepoints

The XSLT Breakpoints / Tracepoints dialog also allows you to edit and remove breakpoints and tracepoints.



setting breakpoints and tracepoints

Breakpoints and tracepoints give you two different ways to see exactly what output is being produced by each instruction in your XSLT file, allowing you to troubleshoot and edit your files efficiently.
Perfecting XSLT Stylesheets

As you’re debugging a stylesheet, the XSLT debugger presents you with several useful pieces of information. To supplement the information shown in the output pane and Trace window, the debugging information windows display additional important details.

The Context information window includes the following tabs:

    * Context: displays the context node and associated attributes or value(s).
    * Variables: displays the global, local, and parameter based variables as well as the name and variable value.
    * XPath Watch: displays the result of XPath 1.0/2.0 expressions, which are evaluated against the root or context node, depending on how they are entered. You can define the XPath expressions you want to monitor here.

Tabs in the Call Stack info window include:

    * Call Stack: displays a list of the previously processed XSL instructions and templates, with the current instruction appearing at the top of the list.
    * Templates: displays all templates used while debugging the current XSLT file. This includes the provided default templates in the built-in template, as well as any included or imported templates.
    * Info: displays information about the type of debugging (XSLT 1.0 or 2.0), the files used, and the debugger status.
    * Messages: displays the xsl:message instruction(s) or any error messages that may occur during debugging.
    * Trace: displays output information for each tracepoint.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Nessus Scan 1 63
I starting with php 12 90
Strange html entity encoding by tidy 14 68
cookies analysis tools 2 24
I will show you how to create a ASP.NET Captcha control without using any HTTP HANDELRS or what so ever. you can easily plug it into your web pages. For Example a = 2 + 3 (where 2 and 3 are 2 random numbers) Session("Answer") = 5 then we…
Browsers only know CSS so your awesome SASS code needs to be translated into normal CSS. Here I'll try to explain what you should aim for in order to take full advantage of SASS.
Viewers will learn about basic arrays, how to declare them, and how to use them. Introduction and definition: Declare an array and cover the syntax of declaring them: Initialize every index in the created array: Example/Features of a basic arr…
The viewer will learn how to dynamically set the form action using jQuery.

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now