From Traditional Integration to Composition – Enterprise Business Services - Applied SOA Patterns on the Oracle Platform - page 270

prefix="urn1"/>
<con1:varNsDecl
namespace="urn:com:telco:ctu:la:messagetrackingdata:v01"
prefix="urn2"/>
<con1:varNsDecl
namespace="urn:com:telco:ctu:la:payload:v01" prefix="urn3"/>
<con1:varNsDecl
namespace="urn:com:telco:ctu:la:messageheader:v01"
prefix="urn4"/>
</con:context>
<con:actions>
<con2:assign varName="taskInput">
<con1:id>_ActionId-3019043452746376819-7d5319e3.13a7dc61937.-76d7</con1:id>
<con2:expr>
<con1:xqueryTransform>
<con1:resource ref="CTUFusion_BUS/Resources/Xquery/
ServiceBroker/XQ_CTUMessage"/>
<con1:param name="messageTrackingData">
<con1:path>$body/urn:CTUMessage[1]/
urn2:MessageTrackingData[1]</con1:path>
</con1:param>
<con1:param name="messageHeader">
<con1:path>$body/urn:CTUMessage[1]/
urn4:MessageHeader[1]</con1:path>
</con1:param>
<con1:param name="Version">
<con1:path>$body/urn:CTUMessage[1]/
urn:Version[1]/text()</con1:path>
</con1:param>
<con1:param name="processHeader">
<con1:path>$body/urn:CTUMessage[1]/
*:ProcessHeader[1]</con1:path>
</con1:param>
<con1:param name="MessageType">
<con1:path>$body/urn:CTUMessage[1]/
urn:MessageType[1]/text()</con1:path>
</con1:param>
<con1:param name="payload1">