aspose file tools*
The moose likes Web Services Certification (SCDJWS/OCEJWSD) and the fly likes JAX-WS async service Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Web Services Certification (SCDJWS/OCEJWSD)
Bookmark "JAX-WS async service" Watch "JAX-WS async service" New topic
Author

JAX-WS async service

a sarkar
Ranch Hand

Joined: Aug 05, 2010
Posts: 92
I understand that async invocation can be used on the client side but is there something on the server side as well? JAX-RS 2.0 introduced a truly async server side capability, wondering if JAX-WS has something similar.


Abhijit
-------
SCJP 5, SCBCD 5, OCWCD 5, OCEWSD 6, CSM
a sarkar
Ranch Hand

Joined: Aug 05, 2010
Posts: 92
To answer my own question, there doesn't seem to be direct support for async service. The service may provide a special method for polling or if the client itself is a Web Service, can callback on a replyTo address.
Frits Walraven
Creator of Enthuware JWS+ V6
Bartender

Joined: Apr 07, 2010
Posts: 1734
    
  25

Just to get an idea with some nice pictures: Oracle Async Web Services.

Regards,
Frits
a sarkar
Ranch Hand

Joined: Aug 05, 2010
Posts: 92
Frits Walraven wrote:Just to get an idea with some nice pictures: Oracle Async Web Services.

I read that. Seems that there is no 1st class support for server side asynchrony; I mean, calling back to a client who itself is a Web Service doesn't seem like 1st class support to me. Thing is, when the client makes an async call, the server will still be busy working on it. Even though the client returns immediately from a non-blocking call, it doesn't reduce the load on the server side.
Frits Walraven
Creator of Enthuware JWS+ V6
Bartender

Joined: Apr 07, 2010
Posts: 1734
    
  25

a sarkar wrote:
I read that. Seems that there is no 1st class support for server side asynchrony; I mean, calling back to a client who itself is a Web Service doesn't seem like 1st class support to me. Thing is, when the client makes an async call, the server will still be busy working in it. Even though the client returns immediately from a non-blocking call, it doesn't reduce the load on the server side.

Agree, it doesn't look like the best support, but when using MDB's at least the load on the server side is handled well. Additional MDB's are pulled in (or pooled in ) when needed.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JAX-WS async service