[NEW ISSUE] SCA Spring C & I specification does not state what happens whena Bean exposed as a service implements mutliple interfaces

Raiser:        
       Mike Edwards

Target:        
        sca-springci-draft-20070926.doc

Description:

It is possible for a Spring Bean in
a Spring Application context to implement more than one interface, which
may in turn be exposed via SCA as a service.

The specification does not say how such
a Bean should be exposed as a service - leaving any runtime implementation
to make a guess.

Proposal:

Where a Spring Bean in a Spring Application
context implements more than one interface which is either explicitly or
implicitly exposed as a service according

to SCA Java rules:

- Each interface is exposed as a separate
service

- The name of each service must be unique.
 Uniqueness is achieved by giving each service is the name "beanName.serviceName",
where beanName is the 

name of the Bean in the application
context and serviceName is the name of the service, where the service name
is EITHER given explicitly via an @Service

annotation in the code OR determined
implicitly from the name of the interface.

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.

Co Chair OASIS SCA Assembly TC.

IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.

Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  

Email:  

Unless stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU