Example

Example 7.4, “Chained Route with Two UMOs” shows a chained route definition that uses two UMOs.

Example 7.4. Chained Route with Two UMOs

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mule-configuration PUBLIC "-//SymphonySoft //DTD mule-configuration XML V1.0//EN"
    "http://www.symphonysoft.com/dtds/mule/mule-configuration.dtd">

<mule-configuration id="RouterConfig" version="1.0":gt;
  <description>Chained routing example</description>
  <mule-environment-properties clientMode="true" />

<endpoint-identifiers>
    <endpoint-identifier name="Processor1" value="vm://message.processor1"/>
    <endpoint-identifier name="Processor2" value="vm://message.processor2"/>
  </endpoint-identifiers>

  ...
    
  <model name="Chained Routers">
  <mule-descriptor name="Processor1" 
                     implementation="demo.hw.processors.BadGuy">
      <inbound-router>
      <endpoint address="Processor1" />
      </inbound-router>
    </mule-descriptor>

  <mule-descriptor name="Processor2"
                    implementation="demo.hw.processors.GoodGuy">
      <inbound-router>
        <endpoint address="Processor2" />
      </inbound-router>
    </mule-descriptor>

  <mule-descriptor name="SoapJms-To-SoapHttp" 
                     implementation="org.mule.components.simple.PassThroughComponent">
      <inbound-router>
        <endpoint address="wsdl-cxf:res:///wsdl/hello_world.wsdl" 
                  streaming="false" synchronous="true" 
                  transformers="InputStreamToString" />
          <properties>
            <property name="service"
                      value="{http://apache.org/hello_world_soap_http}SOAPService" />
            <property name="port"
                      value="{http://apache.org/hello_world_soap_http}SoapOverJmsRouter" />
            <property name="dataFormat" value="message" />
          </properties>
        </endpoint>
      </inbound-router>

      <outbound-router>
      <router className="org.mule.routing.outbound.ChainingRouter">
        <endpoint remoteSync="true" address="Processor1"/>
        <endpoint remoteSync="true" address="Processor2"/>
        <endpoint address="wsdl-cxf:res:///wsdl/hello_world.wsdl"
                    synchronous="true"
                    transformers="StringToInputStream" />
            <properties>
              <property name="service"
                        value="{http://apache.org/hello_world_soap_http}SOAPService"/>
              <property name="port"
                        value="{http://apache.org/hello_world_soap_http}SoapOverHttp"/>
              <property name="dataFormat" value="message"/>
            </properties>
          </endpoint>
        </router>
      </outbound-router>
    </mule-descriptor>
  </model>
</mule-configuration>

The route definition shown in Example 7.4, “Chained Route with Two UMOs” does the following;

	The `endpoint-identifiers` element and its `endpoint-identifier` child elements define how the UMOs can be contacted. In this example, the UMOs are running as local VM components.
	Defines the first UMO and specifies its implementation class.
	Specifies the address at which the UMO is accessed.
	Defines the second UMO.
	Defines the inbound router as a simple pass through router with a single endpoint.
	Specifies that the outbound router is a chaining router. Chaining outbound routers are implemented by the `org.mule.routing.outbound.ChainingRouter` class.
	Specifies that the first UMO, `Process1`, is the first endpoint in the outbound router's chain.
	Specifies that the second UMO, `Process2`, is the second endpoint in the outbound router's chain.
	Specifies the destinaiton endpoint for the message as the last endpoint in the chain.