Hi Christophe Just to check, do you have the <soap:header> element in your port binding to link the 'RelatesTo' message part to the SOAP header?
Regards Gary On Thu, Apr 7, 2011 at 4:24 PM, Christophe Noel <[email protected]> wrote: > Hi list ! > > I'm trying to correlates on a SOAP header, but it doesn't work. > I successfully correlate on the body part (in the following example > "payload"), but this is definitely not my goal. > > Could you please suggest me an workaround ? > > Here is the relevant line from my files. > > In WSDL : > <message name="WaitResponseMessage"> > <part name="payload" element="tns:WaitResponse" /> > <part name="RelatesTo" element="wsa:RelatesTo" /> > </message> > > <vprop:property name="midprop" type="xs:anyURI"/> > <vprop:propertyAlias propertyName="this:midprop" > messageType="tns:CallRequestMessage" part="payload"> > <vprop:query>tns:input/text()</vprop:query> > </vprop:propertyAlias> > <vprop:propertyAlias propertyName="thismidprop" > messageType="tns:WaitResponseMessage" part="RelatesTo"> > <vprop:query>text()</vprop:query> > </vprop:propertyAlias> > > In BPEL : > > <bpel:correlationSets> > <bpel:correlationSet name="midcorr" properties="this:midprop"/> > </bpel:correlationSets> > > <bpel:receive partnerLink="pool1AndPoolForCallPortPlkVar" > portType="tns:CallPort" operation="Call" variable="tnsCallRequestMsg" > createInstance="yes" bpmn:label="Message_Start_Event" > name="Message_Start_Event" bpmn:id="_MBhPcF7GEeCP29BbLN8ASQ"> > <bpel:correlations> > <bpel:correlation set="midcorr" initiate="yes"/> > </bpel:correlations> > </bpel:receive> > > > ... and later > > > <bpel:receive partnerLink="pool0AndPool1ForWaitCallbackPortPlkVar" > portType="tns:WaitCallbackPort" operation="WaitResult" > variable="tnsWaitResultRequestMsg" bpmn:label="Message_Intermediate_Event" > name="Message_Intermediate_Event" bpmn:id="_M6Vt0F7GEeCP29BbLN8ASQ"> > <bpel:correlations> > <bpel:correlation set="midcorr" initiate="no"/> > </bpel:correlations> > </bpel:receive> > > Thanks a lot for your help. > > - > ----------------------------------------------------------------------------- > > E-MAIL DISCLAIMER > > The present message may contain confidential and/or legally privileged > information. If you are not the intended addressee and in case of a > transmission error, please notify the sender immediately and destroy this > E-mail. Disclosure, reproduction or distribution of this document and its > possible attachments is strictly forbidden. > > SPACEBEL denies all liability for incomplete, improper, inaccurate, > intercepted, (partly) destroyed, lost and/or belated transmission of the > current information given that unencrypted electronic transmission cannot > currently be guaranteed to be secure or error free. > Upon request or in conformity with formal, contractual agreements, an > originally signed hard copy will be sent to you to confirm the information > contained in this E-mail. > > SPACEBEL denies all liability where E-mail is used for private use. > > SPACEBEL cannot be held responsible for possible viruses that might corrupt > this message and/or your computer system. > e > ------------------------------------------------------------------------------
