Create a simple Biztalk solution, be sure to have the BPEL compliance set to True, crank up a simple Orchestration like the one shown below, never mind the smart thing going on here :)...
the output here is surpose to be pure BPEL right !?.
<?xml version="1.0"?> <bpel:process xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:q1="jcsharp.net" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="Life.CarrierMoves" targetNamespace="odx.jcsharp.net" xmlns:bpel="http://schemas.xmlsoap.org/ws/2003/03/business-process/"> <bpel:partnerLinks> <bpel:partnerLink name="GreatCarrier" partnerLinkType="q1:GreatCarrierType" partnerRole="portRole" /> <bpel:partnerLink name="NoFuture" partnerLinkType="q1:NoFutureType" partnerRole="portRole" /> <bpel:partnerLink name="CarrierGate" partnerLinkType="q1:CarrierGateType" myRole="portRole" /> </bpel:partnerLinks> <bpel:variables> <bpel:variable name="CarrierMsg" messageType="q1:__messagetype_Life_bustamove" /> </bpel:variables> <bpel:sequence> <bpel:receive partnerLink="CarrierGate" portType="q1:PortType_1" operation="Operation_1" variable="CarrierMsg" createInstance="yes" /> <bpel:switch> <bpel:case condition=" bpel:getVariableData( 'CarrierMsg', 'part', "/*[local-name()='Carrier' and namespace-uri()='http://Life.bustamove']/*[local-name()='dotnet' and namespace-uri()='']") = true()"> <bpel:invoke partnerLink="GreatCarrier" portType="q1:PortType_2" operation="Operation_1" inputVariable="CarrierMsg" /> </bpel:case> <bpel:otherwise> <bpel:invoke partnerLink="NoFuture" portType="q1:PortType_3" operation="Operation_1" inputVariable="CarrierMsg" /> </bpel:otherwise> </bpel:switch> </bpel:sequence> </bpel:process>
well import the darn thing into a Biztalk Server BPEL project, all fine until you compile it... "identifiers beginning with __ are illegal"....
its the q1:__messagetype_Life_bustamove messageType that gets mangled here. Why I have no idea.
When you import the BPEL you can go an rename the messageType, but I would just expect this to work of the shelf......I guess not.
10:00:52 PM
|