On Sun, Dec 4, 2011 at 12:25 AM, Tammo van Lessen <[email protected]>wrote:
> Hi Denis, > > I'm not sure why it fails in this particular case, nor did I use > correlation on header parts yet. However, I'd like to note that, from a > conceptual point of view, using these very WS-A headers in BPEL > correlation seems not to be a good idea. Hi Tammo, By trying this I too felt that it's not going to work out of the box. > Their presence should be > handled and correlated by the Web service stack already (in this case > Axis2) when the respective policies and/or WSDL extensions > (wsaw:UsingAddressing and wsaw:Anonymous prohibited) are set. I recently > experimented with this to support an dual channel transport for two-way > operations in ODE, which worked quite well but only with some mean > tweaks because Axis2 only partially supports the WSDL extensions. I'm > trying to make a patch for Axis and push it a little to have this > feature in ODE as well. > > Is it that what you are trying with the correlation? > yes. > > Thanks, > Tammo > > On 03.12.2011 18:05, Denis Weerasiri wrote: > > On Wed, Apr 13, 2011 at 6:22 PM, Gary Brown <[email protected]> wrote: > > > >> 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? > >> > > Hi, > > I'm trying to write a BPEL which use correlation-set using ws-addressing > > headers (i.e. MessageID and ReplyTo). > > I tried to do this in ODE trunk. But didn't succeed. > > Was anyone able to use soap headers to do bpel correlations? > > > >> > >> 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 > >> > ------------------------------------------------------------------------------ > >>>> > >>> > >> > > > > > > > > -- > Tammo van Lessen - http://www.taval.de > -- Thanks, Denis ---------------------------------------------------------- *Denis Weerasiri* * * <http://wso2.com/>**** <http://wso2.com/>*site: ** https://sites.google.com/site/ddweerasiri/*<https://sites.google.com/site/ddweerasiri/> *blog: **http://ddweerasiri.blogspot.com* <http://ddweerasiri.blogspot.com/> * twitter: **http://twitter.com/ddweerasiri* <http://twitter.com/ddweerasiri>* linked-in: **http://lk.linkedin.com/in/ddweerasiri*<http://lk.linkedin.com/in/ddweerasiri>
