As a workaround, we explicitly copy from the WS-Address header into the partner link using:
<bpel:process ... xmlns:wsa="http://www.w3.org/2005/08/addressing";> ... <bpel:assign> <bpel:copy> <bpel:from variable="myMessage" header="ReplyTo"> <bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0">wsa:Address</bpel:query> </bpel:from> <bpel:to partnerLink="myPartnerLink" /> </bpel:copy> </bpel:assign> ... <bpel:invoke name="myInvoke" partnerLink="myPartnerLink" operation="myOperation" portType="foo:MyPort" inputVariable="myInputVariable" outputVariable="myOutputVariable" /> ... </bpel:process> This uses two extensions of ODE - (a) ability to read from headers<http://ode.apache.org/headers-handling.html>and (b) ability to assign URL's directly to partner links<http://ode.apache.org/user-guide.html#UserGuide-ManipulatingEndpoints> . I haven't had time yet to see why it doesn't behave as expected. I hope this helps! - Regards, Terry On 21 May 2010 12:57, Rafal Rusin <[email protected]> wrote: > This looks like a bug actually. > Could you create jira issue and upload your current test case? (I mean > sample Axis client, process and soapui project). > > On 16 May 2010 06:27, philrm <[email protected]> wrote: > > > > Hi, > > > > I am trying to asynchronously call back an invoker from a BPEL address to > an > > reply address dynamically provided by the invoker with WS-Addressing > > <ReplyTo> headers. > > > > I have started by using the example > > (http://old.nabble.com/file/p27401041/Async.zip) to create such a > process. > > The example includes two service definitions for the server in the server > > WSDL, each with the full address of the service -- including the service > > where the callback is supposed to go. I am now trying to have ODE NOT use > > the WSDL address, but to extract the reply address from the initial call > > from the client. I provide WS-Addressing headers with an <wsa:replyTo> in > > the initial call. > > > > (Also, differing from the example, I only create a "server" BPEL process; > > the client is implemented in AXIS2 in Java; for testing, I use SoapUI > which > > is able to provide WS-Addressing headers). > > > > Unfortunately, ODE seems to ignore the ReplyTo header, and continues to > use > > the original address provided in the WSDL file. > > > > My question: How can I instruct ODE to use the <replyTo>-Address from > > WS-Addressing? > > > > This is on ODE 2.0 beta2. > > > > Thanks! > > > > Phil > > > > -- > > View this message in context: > http://old.nabble.com/WS-Addressing-ReplyTo-URL-Callback-in-ODE-tp28574679p28574679.html > > Sent from the Apache Ode User mailing list archive at Nabble.com. > > > > > > -- > Regards, > Rafał Rusin >
