Nav
You are viewing an older version of this section. Click here to navigate to the latest version.

SOAP Component Reference

The SOAP Component facilitates the publishing, consuming, and proxying of SOAP Web Services within a Mule flow.

Mule leverages Apache’s open-source http://cxf.apache.org/docs/a-simple-jax-ws-service.html[CXF framework] to build Web services. You can create a CXF Web service in Studio by configuring a SOAP component in your Mule flow to perform any of the following CXF Web service operations:

  • publish a simple service

  • publish a JAX-WS service

  • proxy a published service

  • consume a service using a simple client

  • consume a service using JAX-WS client

  • proxy to a service

Using Mule’s SOAP Component, you can also enable WS-security, specify data bindings, and add interceptors to your CXF Web service. For more information about how Mule leverages the CXF framework, consult the CXF Module Configuration Reference.

Adding a SOAP Component/CXF Element

Mule Studio Version 3.3.1 supports corrected databinding in the following types of Web service Operations:

  • Simple service

  • JAX-WS service

  • Simple client

  • JAX-WS client

Mule Studio Version 3.3.0 supports databinding in the following types of Web service Operations:

  • Simple service

  • JAX-WS service

  • Proxy service

  1. Add a SOAP component to your flow, positioning it just after an inbound endpoint, or just before an outbound endpoint.

  2. Open the component’s Pattern Properties panel, then configure the endpoint’s basic attributes according to the table below.

    image

    Field Value

    Display Name

    Enter a unique name for the component, if you wish.

    Operation

    JAX-WS service (default)
    Proxy service
    Simple service
    JAX-WS client
    Proxy client
    Simple client

  3. The configurable elements and attributes of the SOAP component vary according to the type of operation the Web service is performing. Consult the sub-sections below for detailed configuration information.

  1. Add a CXF element to your flow, positioning it just after an inbound endpoint, or just before an outbound endpoint (see code sample below). The types of CXF element available are as follows:

  2. Configure the endpoint’s basic attributes according to the table below.

    Attribute Value

    doc:name

    unique name for component (not required for Mule Standalone)

    
           
                   
                
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    
    #Publishing
         
    <flow name="example_flow1" doc:name="example_flow1">
            <http:inbound-endpoint exchange-pattern="request-response" host="localhost" port="8081" doc:name="HTTP"/>
            <cxf:jaxws-service doc:name="SOAP"/>
    </flow>
      
         
    #Consuming
      
    <flow name="example_flow2" doc:name="example_flow2">
        <cxf:jaxws-client doc:name="SOAP"/>
        <http:outbound-endpoint exchange-pattern="one-way" host="localhost" port="8081" method="POST" doc:name="HTTP"/>
    </flow>
        
        
    #Proxying
        
    <flow name="example_flow1" doc:name="example_flow1">
            <http:inbound-endpoint exchange-pattern="request-response" host="localhost" port="8081" doc:name="HTTP"/>
            <cxf:proxy-service doc:name="SOAP"/>
    </flow>
  3. The configurable elements and attributes of the SOAP component vary according to the type of operation the Web service is performing. Consult the sub-sections below for detailed configuration information.

In 3.x versions of Mule Studio, you could specify an onException attribute for your SOAP Component.
As of Mule 3.3 — because of the improvements to error handling which manage exceptions — you do not need to specify an onException attribute.

Applying Global CXF Configuration

To set up and reuse customized CXF behavior, you must create a global element and reference it within the SOAP component(s) in your Mule flows. The following configuration information applies to all types of Web service Operations (service, client and proxy).

  1. On your canvas, click the Global Elements tab, then click the Create button, then select CXF Configuration from the list of available options. 

    You can also create a Global CXF Element directly from the SOAP component’s Pattern Properties panel. Next to the Config Reference field, click the (plus) icon to open the Global Element Properties panel.

    image

  2. Configure the global CXF configuration attributes according to the table below.

    image

    Field Value Description

    Name

    unique name

    Enter a unique name for the global element, if you wish.

    Configuration Location

    filepath/filename.xml

    If you have created an .xml file that supplies the specifics of how you want your CXF elements to behave, enter the file path of your CXF configuration file.

    Enable Mule Soap Headers

    true (default)
    false

    If set to true (i.e. checked) this attribute ensures that Mule can add a header to a SOAP message when required as part of the message’s processing.
    For example, if your SOAP messages will be processed by a third-party schema which prohibits deviations from very specific message properties and will not process messages with Mule headers, set this attribute to false (i.e. uncheck).

    Initialize Static Bus Instance

    true (default)
    false

    If set to true, (i.e. checked) this attribute ensures that the CXF Web service uses Mule transports instead of CXF transports.

  3. Click the Message Flow tab to return to your canvas.

  4. Open the Pattern Properties panel of the SOAP component, again.

  5. Use the drop down menu in the Config Reference field to select the global CXF element you created.

    image

  6. Click OK to save your changes to the SOAP component.

  1. Above all flows in your Mule project, add a global cxf:configuration element. Refer to code sample below.

  2. Configure the global CXF configuration attributes according to the table below.

    Attribute Value Description

    name

    unique name

    Enter a unique name for the global element, if you wish. (not required for Mule Standalone)

    enableMuleSoapHeaders

    true
    false

    If set to true`,` this attribute ensures that Mule can add a header to a SOAP message when required as part of the message’s processing.
    For example, if your SOAP messages will be processed by a third-party schema which prohibits deviations from very specific message properties and will not process messages with Mule headers, set this attribute to false.

    initializeStaticBusInstance

    true
    false

    If set to true, (i.e. checked) this attribute ensures that the CXF Web service uses Mule transports instead of CXF transports.

    configurationLocation

    filepath/filename.xml

    If you have created an .xml file that supplies the specifics of how you want your CXF elements to behave, enter the file path of your CXF configuration file.

  3. To the CXF element within your flow, add a configuration-ref attribute to reference the global CXF configuration element. Refer to code sample below.


    
            
         
1
2
3
4
5
6
7
<cxf:configuration name="CXF_Configuration" enableMuleSoapHeaders="true" initializeStaticBusInstance="true" doc:name="CXF Configuration" configurationLocation="src/test/resources/filename.xml"/>
 
<flow name="example_flow1" doc:name="example_flow1">
...
    <cxf:jaxws-client doc:name="SOAP" configuration-ref="CXF_Configuration"/>
    <http:outbound-endpoint exchange-pattern="request-response" host="localhost" port="8081" method="POST" doc:name="HTTP"/>
</flow>
Namespace

    
            
         
1
2
3
4
<mule xmlns:cxf="http://www.mulesoft.org/schema/mule/cxf" 
... 
xsi:schemaLocation="
http://www.mulesoft.org/schema/mule/cxf http://www.mulesoft.org/schema/mule/cxf/current/mule-cxf.xsd">

Publishing a Web Service

This sub-section describes how to specify attributes for your Web service. 

For some attributes, enter data according to the automated design method you used to develop your Web service:

  • bottom up method (code first)

  • top down method (WSDL first)

In the General tab of the SOAP component’s pattern properties panel, configure the Web service’s attributes according to the table below.

image

Attribute Simple service JAX-WS service Proxy service Value

Binding ID

x

x

x

Specify the CXF Protocol Bindings which facilitate the mapping of concrete formats and protocols on transports.

Port

x

x

x

Code first: specify the the port generated in the WSDL.
WSDL first: specify the port to which the Java class will bind in the WSDL.

Namespace

x

x

x

Code first: specify the the SOAP namespace generated in the WSDL. Overrides default CXF namespace.
WSDL first: specify the SOAP namespace to which the Java class will bind in the WSDL. Overrides default CXF namespace.

Service †

x

x

x

Code first: where more than one service exists, specify the the service generated in the WSDL.
WSDL first: where more than one service exists, specify the service to which the Java class will bind to the WSDL.

Service Class †

x

x

x

Code first: click the ellipsis (. . .) to specify the Web service interface to which the Java class will bind to the WSDL.
WSDL first: click the Generate from WSDL button to specify the location of the WSDL document (URL or file) Mule should use to identify the service interface. In the Generate from WSDL panel that appears, specify both the location and the Package Name of the source.

Validation Enabled

x

x

x

Set to true (i.e. checked) if you want Mule to perform schema validation on all incoming messages.

Payload

x

Use the drop down menu to select how much of the message should pass through the proxy. (By default, Mule selects body.)
body: Mule passes only the body of the message through the proxying Web service.
envelope: Mule passes the entire envelope of the message, including body and headers, through the proxying Web service.

† mutually exclusive fields

Configure your cxf:jaxws-service, cxf:`proxy-service`, or cxf:simple-service attributes according to the table below. Refer to the code sample below.

Attribute Simple service JAX-WS service Proxy service Value

bindingId

x

x

x

Specify the CXF Protocol Bindings which facilitate the mapping of concrete formats and protocols on transports.

namespace

x

x

x

Code first: specify the the SOAP namespace generated in the WSDL. Overrides default CXF namespace.
WSDL first: specify the SOAP namespace to which the Java class will bind in the WSDL. Overrides default CXF namespace.

 port

x

x

x

Code first: specify the the port generated in the WSDL.
WSDL first: specify the port to which the Java class will bind in the WSDL.

service †

x

x

x

Code first: where more than one service exists, specify the the service generated in the WSDL.
WSDL first: where more than one service exists, specify the service to which the Java class will bind to the WSDL.

serviceClass †

x

x

x

Code first: specify the Web service interface to which the Java class will bind to the WSDL.
WSDL first: specify the location of the WSDL document (URL or file) Mule should use to identify the service interface. Specify both the location and the packageName of the source.

payload

x

Specify how much of the message should pass through the proxy.
body: Mule passes only the body of the message through the proxying Web service.
envelope: Mule passes the entire envelope of the message, including body and headers, through the proxying Web service.

validationEnabled

x

x

x

True or False. Set to true if you want Mule to perform schema validation on all incoming messages.

† mutually exclusive attributes


    
            
         
1
2
3
4
5
6
7
8
# JAX-WS Service
     
<cxf:jaxws-service doc:name="SOAP" bindingId="StockQuote12" namespace="http://www.webserviceX.net" port="8080" service=" " serviceClass="org.mule.example.bookstore.OrderService" validationEnabled="true"/>
 
     
# Proxy Service
     
<cxf:proxy-service doc:name="SOAP"  port="8080"  serviceClass="org.mule.example.bookstore.OrderService"     payload="body" bindingId=" " namespace=" " service="StockQuoter" validationEnabled="true"/>

Consuming a Web Service

This sub-section describes how to specify attributes for your Web service client. 

In the General tab of the SOAP component’s pattern properties panel, configure the Web service client’s attributes according to the table below.

image

Attribute Simple client JAX-WS client Proxy client Value

Operation

x

x

x

Specify the operation to invoke on the Web service to which your client will make calls. For example, createNew.

Service Class

x

x

x

Specify the Java class CXF should use to construct its service model for the client.

Decoupled Endpoint

x

x

x

Specify the reply-to endpoint (URL) for clients which have WS-Addressing enabled.

Client Class

x

Specify the name of the client class that CXF generated using its wsdl2java tool.

Payload

x

Use the drop down menu to select how much of the message the client passes to the service. (By default, Mule selects body.)
body: Mule passes only the body of the message.
envelope: Mule passes the whole envelope of the message, including body and headers.

Port

x

x

Not the TCP port. Specify the WSDL SOAP port name the client must use to communicate with the Web service. Links the binding to the Web service.

Configure your cxf:jaxws-client, cxf:`proxy-client`, or cxf:simple-client attributes according to the table below. Refer to the code sample below.

Attribute Simple client JAX-WS client Proxy client Field Contents

port

x

x

Not the TCP port. Specify the WSDL SOAP port name the client must use to communicate with the Web service. Links the binding to the Web service.

serviceClass†

x

x

x

Specify the Java class CXF should use to construct its service model for the client.

clientClass†

x

Specify the name of the client class that CXF generated using its wsdl2java tool.

decoupledEndpoint

x

x

x

Specify the reply-to endpoint (URL) for clients which have WS-Addressing enabled.

operation

x

x

x

Specify the operation to invoke on the Web service to which your client will make calls. For example, createNew.

payload

x

Specify how much of the message the client passes to the service.
body: Mule passes only the body of the message.
envelope: Mule passes the whole envelope of the message, including body and headers.

† mutually exclusive


    
            
         
1
2
3
4
5
6
7
8
# JAX-WS Client
     
<cxf:jaxws-client doc:name="SOAP"   port="StockQuoter"  serviceClass=" org.mule.example.bookstore.OrderService" clientClass=" " decoupledEndpoint="http://www.StockQuoter.org" enableMuleSoapHeaders="true" operation="createNew"/> 
      
     
# Proxy Client
    
<cxf:proxy-client doc:name="SOAP"   port="8080"  serviceClass="org.mule.example.bookstore.OrderService"  clientClass=" " decoupledEndpoint=" " enableMuleSoapHeaders="true" operation="createNew" payload="body"/>

Adding Custom Interceptors

CXF uses chains of http://cxf.apache.org/docs/interceptors.html[interceptors] – the most basic processing unit – to process messages. As a message moves through an interceptor chain, each interceptor performs an action upon the message, such as reading it, transforming it or validating it.

If you need to add an extra action to the messages processed by your CXF Web service (for instance, to add a header to a message), use the SOAP component to add extra interceptors to the interceptor chain.

  1. Open the Pattern Properties panel, then click on the Interceptors tab.

  2. Click on the (plus) icon to reveal the four Interceptor Providers CXF uses to add interceptors to interceptor chains; click one of the choices to add an interceptor provider.

    • Add in Interceptor

    • Add in Fault Interceptor

    • Add out Interceptor

    • Add out Fault Interceptor

    image

  3. Double-click the newly created interceptor provider in the Settings pane (below, left) to open the interceptor provider panel (below, right). 

    image

  4. Use the drop down menu in the Beans field to select from your list of existing beans the one that will act as an interceptor.

    If you have not yet created any beans, click the new button to open a new Properties Panel that facilitates the creation and configuration of new a bean, which imports the Java class you have built to specify the interceptor’s behavior.
  5. Click the add to list button to insert the selected bean into the interceptor chain.

  6. Click Finish, then OK to save your interceptor configurations.

  1. Above all flows in your Mule project, create a global spring:bean element to import the Java class you have built to specify the interceptor’s behavior. Refer to code sample below.

  2. To the CXF element in your flow, add a child element according to the type of action you want the interceptor to perform:

  3. As a child element of the CXF interceptor element, add a reference to the spring bean, spring:ref bean, you created which imports the Java class.

  4. Add as many as four interceptor child elements to your CXF service or client component.


    
            
         
1
2
3
4
5
6
7
8
9
10
11
12
13
14
<spring:beans>
    <spring:bean id="Bean" name="Bean" class="org.mule.example.myClass"/>
</spring:beans>
     
    
<flow name="example_flow1" doc:name="example_flow1">
...
    <cxf:proxy-service doc:name="SOAP"   port="8080"  serviceClass="org.mule.example.bookstore.OrderService"  payload="body" bindingId=" " namespace=" " service="" validationEnabled="true">
       <cxf:inInterceptors>
           <spring:ref bean="Bean"/>
       </cxf:inInterceptors> 
    </cxf:proxy-service>
...
</flow>

Adding Web Service Security

Enterprise
To protect the CXF Web service in your Mule flow, you can configure elements in the SOAP component to apply WS-security. You can add http://cxf.apache.org/docs/ws-security.html[WS-Security] Configuration Elements (i.e. key-value pairs) to validate and/or authenticate information in the SOAP header of a message; you can also enable one or more of six Token Validators to ensure message security. The ability to add these security features is available only in the Enterprise Edition of Mule Studio.

Consult the Enabling WS-Security document to configure the security elements of your Web service.

Configuring Advanced Elements

You can adjust several advanced CXF Web service configurations according to your requirements.

  1. Open the Pattern Properties panel, then click on the Advanced tab.

    image

  2. Adjust configurations as needed according to the table below, then click OK to save your changes.

Configuration Simple or JAX-WS Service Simple or JAX-WS Client Proxy service Proxy client Activity

WSDL Location

x

x

x

x

In the WSDL Location field, enter the URL (relative or absolute) of the WSDL file which describes the functionality of the Web service.

MTOM Enabled

x

x

x

x

Set MTOM Enabled to true (i.e. checked) if you want Mule to process the binary data sent as part of a SOAP message. (Message Transmission Optimization Mechanism)

Enable Mule Soap headers

x

x

x

x

By default, Enable Mule Soap Headers is set to true (i.e. checked); this ensures that Mule can add a header to a SOAP message when required as part of the message’s processing. Set to false (i.e. unchecked) if you do not want Mule to add headers to SOAP messages. For example, if your SOAP messages will be processed by a third-party schema which prohibits deviations from very specific message properties (such as added Mule headers), deactivate the Enable Mule Soap Headers box.

Soap 1.1
Soap 1.2

x

x

Use radio buttons to select the version of SOAP you want your service to use: SOAP 1.1 or SOAP 1.2. By default, Mule sets the version to SOAP 1.1.

Databinding

x

x

Within the context of the CXF framework, data binding refers to the mapping of data from XML documents to Java objects. Use the drop down menu to select a data binding type that will meet your configuration requirements:
aegis-databinding
jaxb-databinding
• custom-databinding
jibx-databinding

Schema Locations

x

x

Click the (plus) icon in the Schema Locations pane to specify a schemaLocations attribute that identifies a namespace name and description. Reference schemaLocation for additional details.

  1. Within the context of the CXF framework, data binding refers to the mapping of data from XML documents to Java objects. You can specify the databinding of your client or service, if you wish. (Not configurable on proxy service or proxy client.) The following are the different types of databinding available:

  2. To the CXF element in your flow, add a child element according to the type of databinding you want your service or client to use:

  3. As a child element of the CXF databinding element, add one or more spring:propertyelements with either a name and value, or name and reference, to define any databinding properties. Refer to the code sample below. 

  4. Define a cxf:schemalocations attribute, if you wish, to identify a namespace to which your service should refer. (Not configurable on JAX-WS client, simple client or proxy client.) Reference schemaLocation for additional details. To the CXF element in your flow (below any interceptor elements, if you have added any), add a cxf:schemaLocations child element.

  5. Within the cxf:schemaLocations element, add a cxf:schemaLocation child element, to specify the URL of the schema to which your service should refer. Refer to code sample below.

  6. As per your specific needs, configure any of the following CXF service or client attributes according to the table below. Refer to the code sample below.

Configuration Simple or JAX-WS Service Simple or JAX-WS Client Proxy service Proxy client Activity

validationEnabled

x

x

x

x

When se to true, validationEnabled ensures that Mule can add a header to a SOAP message when required as part of the message’s processing. Set to false if you do not want Mule to add headers to SOAP messages. For example, if your SOAP messages will be processed by a third-party schema which prohibits deviations from very specific message properties (such as added Mule headers), set validationEnabled to false.

mtomEnabled

x

x

x

x

Set mtomEnabled to true if you want Mule to process the binary data sent as part of a SOAP message. (Message Transmission Optimization Mechanism)

wsdlLocation

x

x

x

x

Enter the URL (relative or absolute) of the WSDL file which describes the functionality of the Web service.

soapVersion

x

x

Identify the version of SOAP you want your service to use: SOAP 1.1 or SOAP 1.2. By default, Mule uses SOAP 1.1.


    
            
         
1
2
3
4
5
6
7
8
9
10
11
12
13
<flow name="example_flow1" doc:name="example_flow1">
...
<cxf:jaxws-service doc:name="SOAP"   port="8080"  serviceClass="org.mule.example.bookstore.OrderService"      bindingId=" " namespace=" " service=" " validationEnabled="true" mtomEnabled="true" wsdlLocation="src/main/resources" soapVersion="1.2">
    <cxf:jibx-databinding>
        <spring:property name="sample2" ref="reference"/>
        <spring:property name="sample1" value="value"/>
    </cxf:jibx-databinding>
    <cxf:schemaLocations>
        <cxf:schemaLocation>http://mycompany.com/schemas/stockquotes</cxf:schemaLocation>
    </cxf:schemaLocations>
</cxf:jaxws-service> 
...
</flow>

Complete Code Example

Namespace

         
      
1
2
3
4
5
<mule xmlns:cxf="http://www.mulesoft.org/schema/mule/cxf" 
...
xsi:schemaLocation="
...
http://www.mulesoft.org/schema/mule/cxf http://www.mulesoft.org/schema/mule/cxf/current/mule-cxf.xsd">
Example Code

         
      
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
<spring:beans>
 
        <spring:bean id="property-placeholder"
 
            class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
 
            <spring:property name="location"
 
                value="classpath:config.dev.properties" />
 
        </spring:bean>
 
 
 
 
    </spring:beans>
 
    <mulexml:namespace-manager
 
        includeConfigNamespaces="true">
 
        <mulexml:namespace prefix="soap" uri="http://schemas.xmlsoap.org/soap/envelope/" />
 
        <mulexml:namespace prefix="mes" uri="http://www.mule-health.com/SOA/message/1.0" />
 
        <mulexml:namespace prefix="mod" uri="http://www.mule-health.com/SOA/model/1.0" />
 
    </mulexml:namespace-manager>
 
    <data-mapper:config name="admit_subject_to_upsert_patient"
 
        transformationGraphPath="admit_subject_to_upsert_patient.grf"
 
        doc:name="DataMapper" />
 
    <data-mapper:config name="upsert_patient_response_to_create_episode"
 
        transformationGraphPath="upsert_patient_response_to_create_episode.grf"
 
        doc:name="DataMapper" />
 
    <object-to-string-transformer name="Object_to_String"
 
        doc:name="Object to String" />
 
    <data-mapper:config name="create_episode_response_to_admit_subject_response"
 
        transformationGraphPath="create_episode_response_to_admit_subject_response.grf"
 
        doc:name="DataMapper" />
 
    <flow name="admitPatientService" doc:name="admitPatientService"
 
        doc:description="AdmssionService SOAP Web service which accepts calls and processes request to perform pre-admissions activities in the hospital's systems.">
 
        <http:inbound-endpoint exchange-pattern="request-response"
 
            host="localhost" port="${http.port}" doc:name="AdmissionService"
 
            path="AdmissionService" />
 
        <cxf:proxy-service doc:name="Proxy service"
 
            namespace="http://www.mule-health.com/SOA/service/admission/1.0"
 
            payload="body" port="AdmissionPort" service="AdmissionService"
 
            wsdlLocation="service/AdmissionService.wsdl" />
 
        <mulexml:dom-to-xml-transformer
 
            returnClass="java.lang.String" />
 
        <flow-ref name="upsertPatient" doc:name="Upsert Patient" />
 
        <flow-ref name="createEpisode" doc:name="Create Episode" />
 
        <data-mapper:transform
 
            config-ref="create_episode_response_to_admit_subject_response"
 
            doc:name="&lt;createEpisodeResponse /&gt; to &lt;admitSubjectResponse /&gt;" />
 
    </flow>
 
    <sub-flow name="upsertPatient" doc:name="upsertPatient" doc:description="Uploads and inserts patient data into a hospital system.">
 
        <data-mapper:transform config-ref="admit_subject_to_upsert_patient"
 
            doc:name="&amp;lt;admitSubject /&amp;gt; to &amp;lt;upsertPatient /&amp;gt;" />
 
        <flow-ref name="invokePatientService" doc:name="Invoke Patient Service" />
 
        <mulexml:dom-to-xml-transformer
 
            returnClass="java.lang.String" />
 
    </sub-flow>
 
    <sub-flow name="invokePatientService" doc:name="invokePatientService" doc:description="Submits calls to the PatientService Web service.">
 
        <cxf:proxy-client payload="body"
 
            enableMuleSoapHeaders="true" doc:name="Proxy client" />
 
        <http:outbound-endpoint exchange-pattern="request-response"
 
            host="localhost" port="${http.port}" path="PatientService" doc:name="PatientService" password="hello123" user="nialdarbey"/>
 
    </sub-flow>
 
    <sub-flow name="createEpisode" doc:name="createEpisode" doc:description="Creates new episodes for patient pre-admission into the hospital systems.">
 
        <data-mapper:transform config-ref="upsert_patient_response_to_create_episode"
 
            doc:name="&amp;lt;upsertPatientResponse /&amp;gt; to &amp;lt;createEpisode /&amp;gt;" />
 
        <flow-ref name="invokeEHRService" doc:name="Invoke EHR Service" />
 
        <mulexml:dom-to-xml-transformer
 
            returnClass="java.lang.String" />
 
    </sub-flow>
 
    <sub-flow name="invokeEHRService" doc:name="invokeEHRService" doc:description="Submits calls to the EHR Web service.">
 
        <cxf:proxy-client payload="body"
 
            enableMuleSoapHeaders="true" doc:name="Proxy client" />
 
        <http:outbound-endpoint exchange-pattern="request-response"
 
            host="localhost" port="${http.port}" path="EHRService" doc:name="EHRService" />
 
    </sub-flow>
 
</mule> 

See Also