This work is a result of the ScorWare project in which eBM WebSourcing was involved in.

The SCA feature is provided in PEtALS by the SCA JBI Service Engine (link to the component and link to the documentation)

The main advantage of SCA over other approaches, like BPEL or EIP, is that you can define the composition with Java instead of XML. The SCA composite defines services, which are exposed in the bus. It also defines references, which point to services that might be called or used by the composite at runtime. These references define possible dependencies. And eventually, your composite embeds a Java implementation which allows you to manipulate the references as simple Java objects. This makes the user job easier, in particular to call a service operation or test conditions on a service call result.

For more details on SCA, on tools and more, take a look at the links below :

• SCA is a specification defined by the Open SOA consortium.
• SCA is in standardization process by the OASIS Consortium.
• OW2 FraSCAti is the SCA platform the SCA service engine is based on.
• Eclipse SCA Tools exist and are hosted by the SOA Tools Platform project. They can be used with the SCA service engine.
• PEtALS Eclipse tools complete the STP SCA tools for PEtALS specifics (PEtALS Maven plug-in support, packaging for PEtALS…).