When XML is processed, usually there is more to it than one input, on transform, and one output. Rarely is the input in exactly the right format, and rarely can the output be put right where it belongs. And seldom is the transformation which does not require lookups or including data from other sources.
When people speak of 'XML processors' they often mean programs that work with XML. These can include
Using these together as building blocks, powerful and maintainable XML Pipelines can be build for managing anything that even remotely resembles XML.
Pipelines can contain other pipelines. Each pipeline can have any number of input and output "ports" that can be used to connect them together.
Because they can be included within each other, you can break apart tasks by function, and even reuse pipelines within other projects.
Besides using XML Pipelines themselves as building blocks, there are several other classes components that can be used.

<%= ConfigurationManager.AppSettings["SS"] %> supports building using a variety of frameworks, each of which includes its own components. The idea is that we use off-the-shelf or platform components targeted for each execution environment, and supply the missing pieces to round out the package.
Current frameworks include:
In addition to being able to route queries by XPath, conditions can be forced to emit warnings or even to stop the pipeline with an error. This is valuable where you want to validate some data flowing into or out of steps.
Both Saxonica and Xerces have produced excellent XML Schema validators, and we let you choose which you want to entrust your data to.
XSL-FO, whether generated directly or via the XML Publishing and Reporting module, is the perfect vehical for cross-platform document delivery. The deployer lets you choose between the bundled RenderX XEP and Apache FOP processors.
You can choose Saxonica's Saxon XQuery engine, in either Basic or Schema-Aware mode, or the DataDirect XQuery engine for deployment. Both are strong and standards-conformant choices.
We're happy to deploy Saxon 6.x, 8.x or Xerces-J XSLT engines, so you may choose whether you need the simplicity of XSLT 1.0, or the power of XSLT 2.0.
Any of the adapters available can be used as input or output to any of the steps in a pipeline, allowing XML Processing to extend even to non-XML data, such as EDI and flat files.
Using DataDirect XQuery — with its unequaled highly-performant embedded database drivers — access to Oracle, SQL Server, Sybase and DB/2 will scream — and in a good way, not like this.
The <%= ConfigurationManager.AppSettings["SS"] %> Web Service Call Composer lets you build and test a call to a web service. Those saved call references can be included and executed as part of a pipeline.
For more information about how to simplify XML processing with XML Pipeline, watch a brief 4-minute introductory video tutorial entitled: Visual Data Integration with XML Pipeline, or simply download a free trial today.
Whatever your XML Processing your application needs: converting, validating, transforming, querying, publishing or anything else — Stylus Studio has you covered. Download a free trial now!