Cart
|
Home > Online Product Documentation > Table of Contents > Stop and Warning Nodes Stop and Warning NodesStop 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 NodesFigure 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 NodesWarning 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.
|
Map between EDIFACT and X12
Anything can be mapped to anything: EDIFACT to X12 or vice-versa, either to XML, and any of those to flat files or other formats. Both the XSLT and XQuery mappers can help bridge complex formats with ease.
Translating XML documents to X12
In-place, via XSLT and via XQuery are all mechanisms supported for converting XML to X12
XML Operations
Using XML Pipeline it's easy to visually specify a series of XML operations to apply on your XML data, including parsing, validating, converting and transforming, according to the needs of your business application.
Using Relational Data in XML Applications
"Using Relational Data in XML Applications" By Dr. Michael Kay covers an overview of several common use cases and provides insight into the benefits and drawbacks of using the approaches available today including XQuery and SQL/XML.
