Geek Answers Handbook

JAX-WS Asynchronous Client Methods for Calling Web Services

I am researching SOAP-based web services using JAX-WS, and it’s very difficult for me to understand what clients are about. If someone could give me a hand explaining to me some of the topics, I would really appreciate it. I use the SOA book as well as google, but I'm really confused, so why I think here I can get a more accurate answer, focused on what I need.

In this way, we can communicate with web services synchronously and asynchronously. Synchronous communication has the disadvantage that both parties must wait for each other before processing is complete.

Asynchronous clients allow us to exchange asynchronously using two programming models: 1- callback and 2- polling

  • Doubt 1: Can someone please explain to me in a simple way what are the differences, pros and cons of the two models (Callback and Pooling).

Speaking of asynchronous communication, I also understand that there must be a way for the manufacturer (web service) to find the consumer (client) after processing is complete. That is why we are turning.

  • Doubt 2: Could you briefly explain how addressing works? And also what about callback and polling methods?

Just one more thing. The Dispatch API also confuses me a lot. Because they constantly talk about dynamic clients.

  • Doubt 3: . How is the send API related to asynchronous communication if they talk about dynamic clients all the time?
  • 4: 2 API- (MESSAGE PAYLOAD), JAXWS?
+5
1
  • -, , , , (Callback Pooling)

: .
- : /, .
- : , .

: .
  - : , , - ajax , , .
  - : , , , .

2. , ? ?

, . . HTTP , . , , , SMTP. ws-, , , envolope, - .

- , . WSDL. , , WS.

, WS- envolope, , , , , , ..

3. API- , , ?

Future<?> response = dispatch.invokeAsync(T, AsyncHandler);

invokeAsync - . , . . Javax.xml.ws.Response java.util.concurrent.Future, J2SE 5.0. Response get, , .

4. 2 API- (MESSAGE PAYLOAD), JAXWS?
. , -. MESSAGE MODE , SOAP.

+2
source

More articles:


All Articles