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 Getting Started with XQuery in Stylus Studio An XQuery Primer Understanding FLWOR Expressions Building an XQuery Using the Mapper Working with the XQuery collection() Function Debugging XQuery Using DataDirect XQuery® Execution Plans Creating an XQuery Scenario Generating XQuery Documentation Using XQuery to Invoke a Web Service Using Web Services in XQuery Choosing a ddtek:wscall Function Creating a ddtek:wscall Function Examining the wscall Function Block Mapping wscall Functions Example: Querying a Web Service Generating Java Code for XQuery Generating C# Code for XQuery 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 >Mapping wscall Functions < Previous| Next > Mapping wscall Functions In most typical XQuery mapping operations, you map source and target document nodes to function block ports, as shown in Figure 383. Figure 383. Mapping Typical Function Blocks in XQuery Mapper When use a wscall function, however, you map source and target document nodes to schema nodes in the port information blocks, as shown in Figure 383. Figure 384. Mapping a wscall Function Block < Previous| Next >