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: JAVA-56 - When more than one interface with the same unqualified name used in the @Service annotation - a proposal


Hi,

 

I’ve written the following proposal with the intent of starting discussions on this issue before the next SCA-J Face to face.

 

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

 

 

Section 8.18 @Service starting at line 1653 talks about the @Service annotation. It already states at lines 1687 to 1689 that it is the responsibility of the Java implementation code to handle the scenario where it needs to expose two services with the same interface by using sub-classing. This paragraph could just be extended.

 

Proposal:

 

Add words in bold to the paragraph on line 1687:

 

“If a Java implementation needs to realize two services with the same interface or two services with the different interfaces that have the same class name, then this is achieved through subclassing of the interface.”

 

Add the following extra paragraph before line 1690:

 

“If a Java Implementation defines a @Service annotation that lists two interfaces with the same class name, the SCA Runtime MUST stop the deployment of the SCA Contribution”

 

 

Thanks,

 

Mark

Mark Combellack| Software Developer| Avaya | Eastern Business Park | St. Mellons | Cardiff | CF3 5EA | Voice: +44 (0) 29 2081 7624 | mcombellack@avaya.com

 



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