OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue 182: proposal to resolve


Current abstract:

The SCA Spring component implementation specification specifies the how the Spring Framework can be used with SCA.  The goals of this effort are:

Coarse-grained integration: The integration with Spring is at the SCA Component level, where a Spring application context provides a component implementation, exposing services and using references via SCA.  This means that a Spring application context defines the internal structure of an implementation.

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

Start from Spring context: It should be possible to generate an SCA Composite from any Spring application context and use that composite within an SCA assembly.


Replace this with:

The SCA Spring component implementation specification specifies the how the Spring Framework can be used with SCA.  This specification extends the SCA Assembly Model by defining how a Spring Framework application context provides an implementation of an SCA component, including its various attributes such as services, references, and properties and how that application context is used in SCA as a component implementation type. The goals of this effort specification are:

Coarse-grained integration: The integration with Spring is at the SCA Component level, where a Spring application context provides a component implementation, exposing services and using references via SCA.  This means that a Spring application context defines the internal structure of an implementation.

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

Start from Spring context: It should be possible to generate Generation of an SCA Composite from any Spring application context and use that composite within an SCA assembly.


Use this replacement for both abstract and introduction. This should keep them in sync.
If accepted this resolves 1st part of the issue. The 2nd part asks for examples, we already have an AI for Mike to provide those.

-Anish
--



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]