Article: Building Asynchronous Services With SCA
This naming convention made it a little difficult to follow sometimes. I had to re-read the subsequent sentences to figure out whether you were referring to the client or service.
>The reference is connected to the service by a wire...
Connected by a wire?
>The fact that the connection involves a callback is defined by the interface used to describe the service...
So, a dual interface is an interface with both the service and callback interfaces?
>The presence of a element on both the OrderClient reference and on the OrderService service indicates that Web services are the method used to communicate between them.
What element? Are you referring to the <binding.ws/>?
It seems the scenarios for SCA can also be handled by asynchronous client processing with a message queue binding. Although there is more infrastructure involved with asynchronous client process, you get durability and robustness. The client does not need to be online all the time. With SCA, the client has to be available in order for the service to send back the response. what happens to the response message if the client callback is unavailable?
The key point here is that you could do this with an async messaging implemenation where you manage the infrastructure. By using sca you let sca manage that for you and in fact in the IBM products it will generate MDBs etc later on during deployment.
However this is an async call as well asa response so in fact the client doesn't have to be present at the same time. For more detail on error handling see
You may want to print it out
Anatole Tresch Mar 03, 2015