Building the Core – Enterprise Business Flows - Applied SOA Patterns on the Oracle Platform - page 181

WS-Addressing Static Routing Slip: ServiceMix

The code for WS-Addressing is as follows:

<SOAP:Header>
<wsa:MessageID>uuid:aaaabbbb-cccc-dddd-
eeee-ffffffffffff

</wsa:MessageID>
<wsa:ReplyTo>
<wsa:Address>
http://CTU.Order/CRM/Clarify
</wsa:Address>
</wsa:ReplyTo>
<wsa:To SOAP:mustUnderstand="1">
mailto:[e-mail]

The code for Static Routing Slip is as follows:

<eip:static-routing-slip
service="ctuOrder:routingSlip"
endpoint="endpoint">
<eip:targets>
<eip:exchange-target
service="ctuOrder:Service1" />
<eip:exchange-target
service="ctuOrder:Service2" />
<eip:exchange-target
service="ctuOrder:Service3" />
</eip:targets>
</eip:static-routing-slip>

</wsa:To>
<wsa:Action>
http://CTU.Order/Provision/Activate
</wsa:Action>
<wsa:FaultTo>
<wsa:Address>
http://www.w3.org/2005/08/addressing/anonymous
</wsa:Address>
<wsa:ReferenceParameters>
<ctuns:ParameterA
xmlns:ctuns="http://CTU.Order.namespace">
FAULT
</ctuns:ParameterA>
<ParameterB>ServiceBroker</ParameterB>
</wsa:ReferenceParameters>
</wsa:FaultTo>
</SOAP:Header>

Thus, this ultimate implementation of Normalization of an SOA pattern leads to the con-
version of BPEL artifacts into some primitive XML constructs, fulfilling a part of the WS-
Addressing paradigm.

"Stop" you say? Two points must be clarified straightaway:

• Are we reinventing another more lightweight BPEL?
• Intermediate routing within SCA is perfectly covered by a mediator. What's
wrong with it, and why can't we employ it instead of routing slips?

Firstly, BPEL 2.0 is a full-fledged language with quite an extensive syntax. It's no longer a
simple approach with essential "Assign-Invoke" commands. A complex syntax requires a
very smart Interpretation Engine. Look at the construct on the right-hand side of the previ-
ous table. You do not need an engine to execute this; any language with a standard XDK
can execute it gracefully. Even without any XDK, you can execute it using less than a
dozen lines of code. Secondly, it's transportable and portable. WS-Addressing is just fine,