sca-j message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: [sca-j] NEW ISSUE: SCA Spring C & I specification should make typeattribute as optional for <sca:service/> element
- From: Ramkumar R1 <ramkumar_rj@in.ibm.com>
- To: sca-j@lists.oasis-open.org
- Date: Wed, 24 Jun 2009 16:38:49 +0530
Raiser: Ramkumar Ramalingam
Target: SCA Spring C&I
Description:
The SCA Spring Client and Implementation specification should make the
type attribute as optional for the <sca:service/> element in the
SCA Spring Extension Schema.
Lets assume a scenario where the existing
spring application is used as a SCA component, in such cases its possible
to have spring beans that do not have any implemented interfaces. So when
the user wants to explicitly expose a particular spring bean (which does
not implement any interface) as sca service using <sca:service/>
element by just modifying the spring context xml file, then the current
<sca:service/> element does not allow the user to do the same, as
it mandates to specify the interface implemented by the bean as value for
its required type attribute.
Proposal:
For Java implementations, in absence of
annotations, the impl class is used as the interface (§1.2.1.3 of the
OSOA Java Impl spec).
Similarly in this case, the SCA Spring
C&I specs should make the "type" attribute as optional for
the <sca:service/> element,
and allow the users to expose a bean without
any implemented interface as service, by assuming that the impl class to
be used as interface for the service.
Thanks & Regards,
R Ramkumar
Open Source SOA Development - Apache Tuscany
Phone : 91-80-41927623
Email : ramkumar_rj@in.ibm.com
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]