Found that Rafal has applied a fix for correlation on header parts in trunk - is it possible for you to try this version to see whether it has fixed your problem?
Regards Gary On Tue, Apr 12, 2011 at 3:13 PM, Gary Brown <[email protected]> wrote: > Hi Christophe > > It appears from my experiments in riftsaw (which uses ODE), that the > correlation of messages after the first are performed before the code > that associates the header info with the message, and therefore the > properties aren't available. > > So I think this is a bug. If you have a suitable testcase then it > would be good if you could attach it to a jira. > > Regards > Gary > > On Mon, Apr 11, 2011 at 1:18 PM, Christophe Noel > <[email protected]> wrote: >> The second message is ignored. >> >> Christophe. >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf Of >> Gary Brown >> Sent: lundi 11 avril 2011 12:23 >> To: [email protected] >> Cc: Christophe Noel >> Subject: Re: Correlation on SOAP headers >> >> Hi Christophe >> >> Have been trying to put together an example to try this out, but having >> problems for the xpath expression on the subsequent message. >> >> Just wondering what behaviour you are seeing - is it just that your second >> message is ignored or do you get some form of exception? >> >> Regards >> Gary >> >> >> On Fri, Apr 8, 2011 at 9:31 AM, Christophe Noel >> <[email protected]> wrote: >>> Hello Gary, >>> >>> Yes I have in the port binding : >>> >>> <operation name="WaitResult"> >>> <soap:operation style="document" >>> soapAction="onResult" /> >>> <input> >>> <soap:body use="literal" parts="payload"/> >>> <soap:header message="tns:WaitResponseMessage" >>> part="RelatesTo" >>> use="literal" encodingStyle="" /> >>> </input> >>> </operation> >>> >>> Christophe. >>> >>> -----Original Message----- >>> From: [email protected] [mailto:[email protected]] On Behalf >>> Of Gary Brown >>> Sent: vendredi 8 avril 2011 10:26 >>> To: [email protected] >>> Cc: Christophe Noel >>> Subject: Re: Correlation on SOAP headers >>> >>> 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 >>>> --------------------------------------------------------------------- >>>> - >>>> -------- >>> >>> - >>> ---------------------------------------------------------------------- >>> ------- >>> >>> 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 >>> ------------------------------------------------------------------------------ >>> >> >> - >> ----------------------------------------------------------------------------- >> >> 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 >> ------------------------------------------------------------------------------ >> >
