ISSUE-173: SCA Spring C & I specification should mention how implicitservices should be determined for special bean definitions

http://www.osoa.org/jira/browse/JAVA-173

Dave Booz

STSM, BPM and SCA Architecture

Co-Chair OASIS SCA-Policy TC and SCA-J TC

"Distributed objects first, then world hunger"

Poughkeepsie, NY (845)-435-6093  or  8-295-6093

e-mail:

Ramkumar R1 ---07/21/2009 08:24:36 AM---Raiser:   Ramkumar Ramalingam Target:  sca-springci-1.1-spec-WD02.pdf

From:

Ramkumar R1 <>

To:



Date:

07/21/2009 08:24 AM

Subject:

[sca-j] NEW ISSUE: SCA Spring C & I specification should mention how implicit services should be determined for special bean definitions

Raiser:   Ramkumar Ramalingam

Target:  sca-springci-1.1-spec-WD02.pdf

Description:

The SCA Spring Client and Implementation specification should mention how implicit services should be determined for the following bean definition as shown below. 

Scenario 1: 

<bean id="bean1" class="calculator.calculatorImpl" abstract="true"> 

.... 

.... 

</bean> 

Scenario 2: 

<bean id="bean1" parent="calculator.calculatorImp"> 

.... 

.... 

</bean> 

Scenario 3: 

<bean id="bean1" factory-bean="calculator.CalculatorFactory"> 

.... 

.... 

</bean> 

The current specs says that in case of implicit services, if there are no <sca:service/> elements in the application context, then services are defined by each of the top-level <bean/> elements in the application context. For the following scenarios shown above, its not valid to create a service. 

Proposal: 

The specification should state that, for these scenarios the services will not be defined and these beans will be ignored for exposing as service. 

Thanks & Regards,

R Ramkumar

Open Source SOA Development - Apache Tuscany

Phone : 91-80-41927623

Email  :