Ready for InfoQ 3.0? Try the new design and let us know what you think!

Service Component Architecture Forges Ahead

| by Miko Matsumura Follow 0 Followers on Jul 27, 2006. Estimated reading time: 1 minute |

The Service Component Architecture group announced nine new members including Cape Clear, Primeton Technologies, Progress Software, Red Hat, Rogue Wave Software, Software AG, Sun Microsystems and TIBCO. These companies join BEA Systems, Inc.,  IBM Corporation, Interface21, IONA Technologies PLC, Oracle, and SAP AG in this multi vendor specification initiative.

This group also announced a wiki based web site called OSOA.ORG, which stands for Open Service Oriented Architecture Organization. Specifications and early implementations of SCA and SDO (Service Data Objects) will be published on this site. This site is intended to collect feedback about early work on these specifications and implementations going forward.

Two major items of development in the spec include an emphasis on simplification of bindings and policy work for enterprise developers to simply and the ability for developers to declaratively supply policy hints. The simplification included the elimination of many special cases to create a single comprehensive composite model. The capability of declaratively supplying policy hints in development include examples such as for security policy you can specify none, basic, or certificate based policies. An internal Job Application service may not need security, but for example salary service may require security. Hints can be included as part of the development process.

The technology reach for SCA now includes BPEL, PHP Spring and EJB, which means a variety of implementation languages can be used to manifest SCA components.

SCA was formed less than 8 months ago, the current focus is on rapid technology innovation and are working towards completion of SCA and SDO specifications. The remaining work is to incorporate feedback and make documents consistent. The organization also wants to incorporate feedback from early implementations including the open source work. The second priority is to standardization. The goal is to turn this work over to a standardization body--and to validate the most appropriate standards body to govern this by the end of this year. The two criteria include the Web Services specialization as well as metadata--so also model driven development. Compared to the OASIS work with SOA Adoption Blueprints, their work is more at the best practices level as opposed to the core technologies level, and is therefore at a different level of abstraction.

Rate this Article

Adoption Stage

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.

Tell us what you think

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

Email me replies to any of my messages in this thread

Re: Microsoft by Jim Murphy

I would say they don't, or rather they are chosing not to line up directly with these efforts.

The SCA and SDO specs seem tangled to me in a way that makes a comparison difficult to do. SDO for example lines up under ADO.NET, but ADO.NET is an implementation technology only and best practices recommend not exposing it directly in service interfaces. Seems SDO is more "visible" which honestly never made that much sense to me - or maybe I don't quite get it.

I don't see MS embracing SCA either. The component model for WCF is based around the .NET Framework plain and simple.

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

Email me replies to any of my messages in this thread

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

Email me replies to any of my messages in this thread

1 Discuss