ISSUE-184: Method Exclusion

[David Booz <booz@us.ibm.com>]

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

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:booz@us.ibm.com

Bryan Aupperle---09/14/2009 09:51:30 AM---TARGET: Java CAA CD03 DESCRIPTION:

From:	Bryan Aupperle/Raleigh/IBM@IBMUS
To:	sca-j@lists.oasis-open.org
Date:	09/14/2009 09:51 AM
Subject:	[sca-j] NEW ISSUE: Method Exclusion

---

TARGET: Java CAA CD03

DESCRIPTION: 
Section 11 - WSDL to Java and Java to WSDL - states that the mapping rules defined by JAX-WS are used and goes on to point out the equivalence of the SCA @OneWay annotation and the JAX-WS @OneWay annotation.  However, there is no discussion of the impact of a @WebMethod with exclude="true" on the SCA interface.  One could read this as only impacting the Java to WSDL mapping and not applying if the Java interface is used in both a service and a reference, and thus the method is not excluded, or, since the interface is remotable, one could read this as the mapping to WSDL must always be applied and the method is excluded from the interface in all circumstances. 

There is also currently no way to exclude a method from a local interface.

PROPOSAL:
Direction: 
1) Text should be added clarifying that if @WebMethod with exclude="true" the the method is excluded from the interface in all circumstances 
2) Add an @Method annotation that allows a method to be excluded. 

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com