|Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite
11g Release 1 (22.214.171.124.0)
Part Number E10224-09
This chapter describes how to use multiple part (multipart) messages with the Oracle Mediator service component.
This chapter includes the following sections:
Oracle Mediator includes support for importing multipart WSDL files in the Mediator Editor.
Oracle Mediator supports working with multipart source and target messages, which include multipart filter expression building, multipart schema validation, and transformations between multipart source and target messages for requests, replies, faults, and callbacks.
The Mediator Editor with a multipart source appears as shown in Figure 20-1.
Figure 20-1 Mediator Editor for a Multipart Source
This section describes how to work with different types of multipart messages.
This section describes multipart request messages.
If you specify a filter expression for a multipart message, then the Expression Builder displays all message parts under the in variable, as shown in Figure 20-2:
Figure 20-2 Expression Builder for a Multipart Request Source
If you add a validation for a multiple part message, then the Add Validation dialog displays a list of parts from which you can choose one part, as shown in Figure 20-3. You specify a Schematron file for each request message part. Oracle Mediator then processes the Schematron files for the parts.
Figure 20-3 Add Validation Dialog for a Multipart Request Source
If you create a new mapper file for a multipart message, then the generated mapper file shows multiple source parts in the XSLT Mapper, as shown in Figure 20-4:
Figure 20-4 XSLT Mapper for a Multipart Request Source
If you assign values using a source expression, then the Expression Builder shows an in variable for each message part. This is the same as specifying filter expressions.
The method to create transformations and assign values to multipart reply, fault, and callback source messages is the same as working with request source messages.
Note:You cannot specify filter expressions or add validations for reply, fault, and callback messages.
If a routing target (that is, a request, reply, fault, or callback) has a multipart message, then the transformation is handled in a slightly different way. This is because the XSLT Mapper does not support multipart targets. In such a case, the Oracle Mediator creates and coordinates a separate mapper file for each target part, as shown in Figure 20-5:
Figure 20-5 Request Transformation Map for a Multipart Routing Target