Chapter 1: Getting Started with Stylus Studio® Chapter 2: Editing and Querying XML Chapter 3: Converting Non-XML Files to XML Chapter 4: Converting EDI to XML Chapter 5: Working with XSLT Chapter 6: Creating XSLT Using the XSLT Mapper Chapter 7: Debugging Stylesheets Chapter 8: Defining XML Schemas Chapter 9: Defining Document Type Definitions Chapter 10: Writing XPath Expressions Chapter 11: Working with XQuery in Stylus Studio Chapter 12: Composing Web Service Calls Chapter 13: Working with WSDL Documents Chapter 14: Building XML Pipelines What is an XML Pipeline? Example of an XML Pipeline in Stylus Studio XML Pipeline Terminology XML Pipeline Semantics 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 Generating Code for an XML Pipeline XML Pipeline Node Properties Reference Chapter 15: Publishing XML Data Chapter 16: Integrating with Third-Party File Systems Chapter 17: Extending Stylus Studio Chapter 18: The Stylus Studio Java API Chapter 19: Stylus Studio GUI Reference

Home >Online Product Documentation >Table of Contents >XML Pipeline Semantics < Previous| Next > XML Pipeline Semantics The following semantics govern the behavior of an XML pipeline: A node is executed only when all its input ports are "filled". A node's input port is "filled" either when it contains a default value that is a reference to a URL or a literal value, or when it is connected to another node's output port and this node provides data that is available. Default values are used only if no pipe is present for that port. When data is available on a node's output port, it is provided to the input ports of all the nodes to which it is connected. A node's input port can be filled by 0 or 1 value. If more than one value becomes available, this is an error and XML pipeline processing aborts. < Previous| Next >