Dashboard > Open SOA > ... > Service Component Architecture Home > Spring Client & Implementation
Log In   View a printable version of the current page.
Spring Client & Implementation
Added by Graham Barber (IBM), last edited by Graham Barber (IBM) on Apr 12, 2007  (view change)
Labels: 
(None)


Spring Client & Implementation Specification

The SCA Java Client and Implementation model for Spring specifies how the Spring Framework can be used with SCA.  The goals of this effort are:

Coarse-grained integration: The integration with Spring will be at the SCA Composite level, where a Spring application context provides a complete composite, exposing services and using references via SCA.  This means that a Spring application context defines the internal structure of a composite implementation.

Start from SCA Component Type: It should be possible to use Spring to implement any SCA Composite that uses WSDL or Java interfaces to define services, possibly with some SCA specific extensions.

Start from Spring context: It should be possible to use any valid Spring application context as the implementation of a component within SCA.  In particular, it should be possible to generate an SCA Composite from any Spring context and use that composite within an SCA assembly.

What's New 

Only small fixes have been made since the 0.95 version of this specification. 

References

The Power Combination of SCA, Spring & OSGi Technologies
Service Component Architecture Specifications

Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.4.5 Build:#708 Apr 12, 2007) - Bug/feature request - Contact Administrators