Library Link To Toggle Frames Print Feedback

Example

Example 6.1, “Basic SOAP/HTTP to SOAP/JMS Route” shows a definition for a basic route that connects a SOAP/HTTP consumer to a SOAP/JMS service.

Example 6.1. Basic SOAP/HTTP to SOAP/JMS Route

...
1      <mule-descriptor name="BasicHTTPtoJMSRoute"
2                       implementation="org.mule.components.simple.PassThroughComponent">
3        <inbound-router>
4          <endpoint address="wsdl-cxf:res:///wsdl/hello_world.wsdl"
                      synchronous="true"
            <properties>
5              <property name="service"
                          value="{http://apache.org/hello_world}SOAPService" />
6              <property name="port"
                          value="{http://apache.org/hello_world_soap_http}SoapOverHTTP" />
7              <property name="dataFormat" value="message" />
            </properties>
          </endpoint>
        </inbound-router>
        <outbound-router>
8          <router className="org.mule.routing.outbound.OutboundPassThroughRouter">
9             <endpoint address="wsdl-cxf:res:///wsdl/hello_world.wsdl"
                       synchronous="true"
                <properties>
10                  <property name="service"
                            value="{http://apache.org/hello_world}SOAPService" />
11                  <property name="port"
                            value="{http://apage.org/hello_world}SOAPOverJMS" />
12                  <property name="dataFormat" value="message" />
                </properties>
              </endpoint>
          </router>
        </outbound-router>
    </mule-descriptor>
...

The route definition shown in Example 6.1, “Basic SOAP/HTTP to SOAP/JMS Route” can be explained as follows:

1

The mule-descriptor defines the route.

2

The implementation attribute specifies that this route uses the simple pass through UMO supplied with Celtix Enterprise.

3

The inbound-router element contains the elements that define the inbound endpoint.

4

The endpoint element specifies how the inbound endpoint is configured.

.The address attribute specifies where the WSDL contract defining the service interface used by the endpoint is located.

5

The service property specifies the QName of the wsdl:service element that contains the definition of the consumer with which the inbound endpoint will interact.

6

The port property specifies the QName of the wsdl:port element that defines the consumer with which the inbound endpoint will interact.

7

The dataFormat property specifies that this endpoint uses the message data mode.

8

The router element specifies that this route is implemented by the pass through router supplied with Celtix Enterprise.

9

The endpoint element specifies how the outbound endpoint is configured.

.The address attribute specifies where the WSDL contract defining the service interface used by the endpoint is located.

10

The service property specifies the QName of the wsdl:service element that contains the definition of the service with which the outbound endpoint will interact.

11

The port property specifies the QName of the wsdl:port element that defines the service with which the outbound endpoint will interact.

12

The dataFormat property specifies that this endpoint uses the message data mode.