• 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
    • Types of Nodes
    • Adding Nodes to an XML Pipeline
    • XQuery and XSLT Nodes
    • XSL-FO Nodes
    • Pipeline and Related Nodes
    • Validate Nodes
    • Choose Nodes
    • ConvertToXML and ConvertFromXML Nodes
    • Stop and Warning Nodes
      • Stop Nodes
      • Warning Nodes
    • HTML Tidy Nodes
    • XML Parser Nodes
    • XML Serializer Nodes
  • Working with the XML Pipeline Diagram
  • Debugging an XML Pipeline
  • 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 > Stop and Warning Nodes

Stop and Warning Nodes

Stop and Warning nodes are used to indicate exceptions to or special conditions encountered in an XML pipeline's execution. They serve a similar purpose, but behave in different ways.

Stop Nodes

Figure 426, for example, shows a Stop node piped to the Output invalid output port of the Validate node - if the validation using the XML Schema specified in the Validate node fails, the Stop node aborts XML pipeline processing, and a user-defined error message is generated. Stop nodes do not have an output port - XML pipeline processing ends if it encounters a Stop node.

Warning Nodes

Warning nodes, like the one shown in Figure 427, do have an output port. When encountered in XML pipeline processing, a Warning node generates the user-defined error message you give to it and pipes the input it is given through to the next node in the XML pipeline.