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

Reply via email to