The great thing about the Service Component Architecture (SCA) standard -on which Oracle SOA Suite 11g is based- is that you do not need to expose low-level mediator services and adapter functionality as a separate external service.
The Eclipse SOA Tools Platform (STP) plug-in and Apache Tuscany simplifies services development through the use of the popular Eclipse development environment. Apache Tuscany has also been integrated with the STP to provide a Service Component Architecture (SCA) Java run time for the services you create, allowing you to annotate your service using the SCA standard and Apache Tuscany annotations. In this tutorial, you will see STP and Apache Tuscany in action, through the creation of a Remote Method Invocation (RMI) service.
Oracle's SOA suite AS11 provide all of these as a comprehensive and well integrated product suite. If someone wants to logical group the components separately to reposition them in these categories then it could be like:
SCA introduces a programming model that embraces O-O for in-process calls but provides facilities for asynchronous, loosely-coupled interactions for remote operations.
SCA introduces a programming model that embraces O-O for in-process calls but provides facilities for asynchronous, loosely-coupled interactions for remote operations.
An interesting but rather high level IBM white paper showing how SCA, Spring, and OSGi can be used together to implement SOA. I wished for some code examples.
An interesting but rather high level IBM white paper showing how SCA, Spring, and OSGi can be used together to implement SOA. I wished for some code examples.