I have to expose some Java method as an asynchronous Web service. WS-Addressing must be supported. An implementation code of this method should retrieve somehow WS-A replyTo information and call another Web service on replyTo URL to push the results.
I was asked to use WS-A for that and NOT provide explicitly in API special parameter with addressing information. Here are my questions : 1. Can I use WS-Addressing for that? I am doubt. As I understand the goal of WS-Addressing spec is to allow sender to send a message to a recipient without having to care about the message routing details. The WS infrastructure can decide how to address message using as many intermediaries as necessary. This addressing is transparent for both sender and recipient application code. What I am trying to do is to use WS-Addressing for application level dispatching ... Is it correct ? 2. If API is not one-way, WS infrastructure automatically recognize replyTo header and send response to it. Can I avoid it ? 3. How can I access WS-A headers in the application code? (I do not want to use JAX-RPC handlers - put them on TLS and access this local storage from the application code). Can I do it another way? This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
