BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage News Article: Building Asynchronous Services With SCA

Article: Building Asynchronous Services With SCA

Bookmarks
The Service Component Architecture has generated a lot of debate since its initial release in 2005. Although there has been a lot written about the actual specifications, there has been little on what a developer would be presented with. In this exclusive InfoQ article, Mike Edwards from IBM and one of the co-authors of the specifications, writes about how to develop asynchronous services using SCA.

Rate this Article

Adoption
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Confused.

    by An Phu,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    >For the OrderClient, there is a reference with the name "OrderService". On the OrderService there is a service with the name "OrderService".



    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?

  • Re: Confused.

    by mike prendergast,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    "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
    www.ibm.com/developerworks/websphere/library/te...
    You may want to print it out

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT