• Chapter 1: Getting Started with Stylus Studio®
• Chapter 2: Editing and Querying XML
• Chapter 3: Converting Non-XML Files to XML
• Chapter 4: Working with XSLT
• Chapter 5: Creating XSLT Using the XSLT Mapper
• Chapter 6: Debugging Stylesheets
• Chapter 7: Defining XML Schemas
• Chapter 8: Defining Document Type Definitions
• Chapter 9: Writing XPath Expressions
• Chapter 10: Working with XQuery in Stylus Studio
• Chapter 11: Composing Web Service Calls
• Chapter 12: Accessing Relational Data as XML
• Chapter 13: Building XML Pipelines
  • What is an XML Pipeline?
  • The XML Pipeline Editor
  • Steps for Building an XML Pipeline
  • Planning an XML Pipeline
  • Use Case: Building order.pipeline
  • Working with Nodes
  • Working with the XML Pipeline Diagram
  • Debugging an XML Pipeline
    • Cross-Language Debugging
    • Execution Framework Determines Debugging Support
    • Setting and Removing Breakpoints
    • Running the Debugger
    • Stepping Into a Node
    • Stopping Debug Processing
  • Generating Code for an XML Pipeline
  • XML Pipeline Node Properties Reference
• Chapter 14: Publishing XML Data
• Chapter 15: Integrating with Third-Party File Systems
• Chapter 16: Extending Stylus Studio
• Chapter 17: The Stylus Studio Java API
• Chapter 18: Stylus Studio GUI Reference

Home > Online Product Documentation > Table of Contents > Running the Debugger

Running the Debugger

To run the debugger, click the Start Debugging button ( ) or click F5:

When the debugger hits a breakpoint you have set, it displays a pause symbol, like the one shown in Figure 433.

Figure 433. Pause Symbol for a Debugging Breakpoint

When debugging is paused, debugging tools (like those that let you step into and over breakpoints, and toggles for the Watch, Variables, and Call Stack windows) become active. You cannot edit the XML pipeline or alter its scenario properties during debugging, or when the debugger is paused.

Figure 434. Debugging an XQuery Node in order.pipeline

Figure 434 shows a breakpoint set on the createFullOrder.xquery node in order.pipeline. The Preview window shows the XML pipeline's execution log, and we can see in it that the two ConvertToXML nodes have just been processed; this is confirmed by the presence of the pause symbol on the following XQuery node - it has not yet been processed. The Variables window shows the data retrieved from booksXML.txt.