[NEW ISSUE] Spring C&I spec: interface of a service when no <sca:service>element is present

[Anish Karmarkar <Anish.Karmarkar@oracle.com>]

Since I haven't seen any response to this email, I'm filing a new issue.

Title: interface of a service when no <sca:service> element is present

Specification: Spring C&I spec

Description:

Line 457 of [1] says: "interface.java child element is present with the
@interface attribute set to the fully qualified name of the interface
class introspected from the bean class declared in the @class attribute
of the <bean/> element."

What happens if the class implements multiple interfaces? The 
specification leaves it open wrt which interface gets picked. This is 
different than the POJO CI spec. It also does not address the case where 
the class does not implement any interfaces.

Proposed direction for resolution:

Align this with the POJO CI spec. If the class does not implement any 
interfaces then use the fully qualified class name as the value for the 
interface.java/@interface attribute. If the class implements multiple 
interfaces then introspect multiple sca service, one for each interface 
with the appropriate value set of the attribute interface.java/@interface.

-Anish
--


[1] 
http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/39024/sca-springci-1.1-spec-WD05.pdf 


On 10/10/2010 8:01 PM, Anish Karmarkar wrote:
> Line 457 [1] says: "interface.java child element is present with the
> @interface attribute set to the fully qualified name of the interface
> class introspected from the bean class declared in the @class attribute
> of the <bean/> element."
>
> What happens if the class implements multiple interfaces?
> Why is introspection necessary, wouldn't it be easier to just set it to
> the value of the @class attribute.
>
> Wanted to see if others see this as an issue as well before I file one.
>
> Thanks.
>
> -Anish
> --
>
> [1]
> http://www.oasis-open.org/apps/org/workgroup/sca-j/download.php/39024/sca-springci-1.1-spec-WD05.pdf
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>