Thursday, July 23, 2009

Tuscany 2.0 Milestone 3 released

Today we released the third milestone release of the new Tuscany 2.0 SCA runtime, this is another step towards the fully OASIS specification compatible SCA runtime that we aim to have finished later this year when the final versions of the OASIS SCA specifications are released.

This Tuscany release includes lots of updates for OASIS spec compliance, along with new 2.x support for BPEL and Spring components, and support for SCA contributions as ZIP archives which enables using contribution specific application dependencies.

One other exciting new feature in this M3 release is the new tuscany.war distribution for SCA enabling Apache Tomcat. This makes updating Tomcat to support SCA really simple - deploy the war to Tomcat, go to the Tuscany admin application, click on install, and thats it, on a restart of Tomcat it can now run SCA contributions and SCA enabled Web applications.

In subsequent Tuscany releases this Tomcat integration will be enhanced to use the improved SCA domain support being developed in the Tuscany 2.x code so that SCA domains can be easily managed and created spanning applications as well as runtime instances and clusters.

To find out more and to check out the release go to the Apache Tuscany website

Monday, July 06, 2009

Article: Communication Flexibility Using Bindings

Take a look at this article written by some members of the "Tuscany Community"

This article is taken from the book Apache Tuscany in Action. It looks at how bindings are used to configure wire protocols for a component's service connections. One of the most important features of SCA is its support for a wide variety of communication protocols. If your services need to talk Web Services, JMS, CORBA, RMI, or REST, they can do it using SCA and Tuscany. If they need to use some specialized or proprietary protocol to meet a particular application need, that's fine too. Even better, your business code doesn't need to know which protocol it's using; the choice of a protocol is made by (you guessed it) the component's configuration. How cool is that? The piece of SCA magic that makes all this possible is called a binding.

In this article, we'll see how to use bindings on services and references, and what it means if no bindings are configured. Finally we'll take a look at the SCA domain and see how bindings relate to communication within and outside an SCA domain.

Labels: ,