For Java developers, it’s now possibly to create an SCA assembly definition and then generate Java code from it. And, if you want to start with some Java you already have, we’ve added a special introspector that will investigate your code and automatically produce an SCA assembly.

Once you’ve created your Java SCA project, you can then run and debug it using the great facilities that Eclipse provides.

We also have made sure that the SCA artifacts you might create are properly validated, helping you spot mistakes early in the process.

We even took the time to update the graphics, giving us a prettier SCA Composite Designer.

For me, the most exciting feature is how we’ve developed the core SCA model to be extensible by people who want to write in extra capabilities into the tools. The heart of the model contains the SCA standard specifications, and different extensions have been created to support the key Open Source SCA runtimes - Apache Tuscany 1.4 and Frascati 0.5. Using the extension mechanisms, it is much more straightforward to add new concepts to SCA and extend the tools to include them.

SCA Tools has been improved a lot. Download SCA Tools 2.0.0 now!

• The tutorial, Towards Integrated SOA Development with Eclipse STP and Swordfish (Monday, 13:30, 4 hours, Room 207), is not exclusively about SCA. It demonstrates how SOA applications can be developed and run using the tools and runtimes provided by the STP project and the Swordfish project.
• Vincent will also present the new & noteworthy features of the SCA Tools project (Tuesday, 13:50, 10 minutes, Room 209/210). This talk will be part of the track titled “SOA Track Set” that is a collection of short talks about different STP projects.

You can check the status of the build on the Eclipse Hudson server. You will need to log in with your build.eclipse.org credentials to see the results. On that page you will find zip files which are archived update sites of the builds.

Two components of the STP (SOA Tools Platform) project are closed (STP-SC and STP-SOAS). But, it’s not a negative sign. On the contrary! It’s a sign of maturity.

These two components are closed because for a while now they were no longer maintained. But STP is not dead. Last year, the STP project grew with the arrival of many new tools for SOA: STP-IM, STP-Policy, STP-EID, SCA Tools. These components/projets are still alive and they are very active. More over, the ‘historical” components of STP have never been so active. Since two weeks, the BPMN modeler is a sub-project of STP.

So, it was the time for STP to be restructured to keep a clear line.

Thanks to Laurent, from the EMF Compare project, I added a gradient of color on each element of the modeler.

Before:

Now:

I think it’s better, what do you think?

Currently, the SCA designer with these new colors is only available on the svn. However, we plan to provide quickly a new build.
This build will provide another new feature: extension points to add easily new/specific SCA elements in the designer (Thanks Norihiro!).

As usual, if you want to know more about the SCA Tools project, please have a look at our wiki.

Next steps?
Many new features are planned or already available in the svn:

• An XML editor for assembly files and component types (svn)
• Some tools to test SCA applications (planned)
• An editor for composite files based on Eclipse forms (planned)
• Meta model extensibility, SCA Composite designer extensibility also (in progress)
• New icons (svn)
• SCA nature and SCA perspective (svn)
• New colors for the SCA Composite Designer (less aggressive
• … have a look on the SCA Tools wiki

Any contribution/suggestion/help is welcome…