> Transforming Data Using the XQuery Mapper > Introduction

Transforming Data Using the XQuery Mapper

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Introduction

BEA XQuery Mapper is a graphical mapping tool that enables you to transform data between XML, non-XML, and Java data types, allowing you to integrate heterogeneous applications rapidly. For example, you can package data transformations in BEA WebLogic Integration (WLI) as controls and reuse the controls in multiple business processes and applications. You can also use .xq files created in XQuery Mapper as resources in BEA AquaLogic Service Bus (ALSB).

The output of XQuery Mapper is a query in the XQuery language, which is defined by the World Wide Web Consortium (W3C). For more information about W3C and the XQuery language, see http://www.w3.org/XML/Query/.

Overview of XQuery Mapper

You can use XQuery Mapper to transform data between XML, non-XML, and Java data types. For example, XML data that is valid against one schema can be converted to XML that is valid against a different schema. The data can be based on XML schemas, Web Service Definition Language (WSDL) file, and Message Format Language (MFL) files.

When you select the Simple source type, you can transform standard schema types, such as boolean, byte, double, float, int, long, short, String, and Date, to any other required target data format.

A data transformation can have multiple input types, but only one target type. For example, data can be transformed from two sources to one target, as shown in the following figure.

Figure 1-1 Data Transformation from Multiple Sources to One Target

Data Transformation from Multiple Sources to One Target

Support for XQuery 2002 and 2004

WLI supports data transformation for the following versions of XQuery:

When you open an XQuery 2002-compliant XQuery file, it opens automatically in the XQuery 2002 Transformation Editor, which has Source and Test views, but no Design view.

Restrictions Applicable to the XQuery Test View

Table 1-1 Restrictions Applicable to the XQuery Test View
Restriction
Applicable to XQ2002?
Applicable to XQ2004?
If an XQuery calls a Java user function, the Java method must be static.
Yes
Yes
If an input Java type argument to an XQuery is an abstract class or an interface, the test view can not process it. An error message is displayed in the results view.
Yes
No
The input Java type and its member variables (except those of type primitive, String, java.sql.Date and java.util.Date) must follow the standard Java Bean guidelines.
Yes
No

Upgrading from XQuery 2002 to 2004

When you upgrade a WLI 8.1 project to 10.2, by default, XQuery 2002-compliant code that is embedded in JPD files (inline XQuery code) is not converted to XQuery 2004. You can choose to convert the inline XQueries from XQuery 2002 to XQuery 2004, by performing the following steps in the Source Upgrade screen of the upgrade wizard.

  1. Expand JPD Document Upgrader options, as shown in the following figure.
    2. Figure 1-2 Workshop 8.1 Application Upgrade


    Workshop 8.1 Application Upgrade

  2. Select the Upgrade XQ2002 to XQ2004 check box, as shown in the following figure.
    3. Figure 1-3 Workshop 8.1 Application Upgrade


    Workshop 8.1 Application Upgrade

Note: Selecting the Upgrade XQ2002 to XQ2004 check box in the upgrade wizard has no effect on the XQuery 2002-compliant XQuery files. They are not converted automatically to XQuery 2004. You can upgrade XQuery 2002-compliant XQuery files in a project to XQuery 2004, by right-clicking the file in the Navigator view and choosing Upgrade to XQuery 2004.

Topics Included in This Guide


  Back to Top       Previous  Next