<%@ page language="C#" masterpagefile="~/templates/Documentation.master" inherits="Page" pagetitle="How Stylus Studio Uses Integrated Components" keywords="How Stylus Studio Uses Integrated Components"%>
  • 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
  • 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 >How Stylus Studio Uses Integrated Components

    < Previous| Next >

    How Stylus Studio Uses Integrated Components

    Stylus Studio uses the DataDirect XQuery® and XML Converters engines to process XQuery and XML conversions. These processing engines run under the covers throughout Stylus Studio - in the XQuery module, EDI to XML Conversions module, XML Pipelines module, and the Custom XML Conversions module, to name a few.

    You can also use the APIs for these components to build and test applications that run outside Stylus Studio. You might, for example, want to build an XQuery application using Java or C# code for .NET generated by Stylus Studio for the XQuery you develop using the Stylus Studio XQuery module.

    < Previous| Next >