ISSUE 216: Resolution of Issue 201 is insufficient

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

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:

|------------>
| From:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Bryan Aupperle/Raleigh/IBM@IBMUS                                                                                                                  |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                        |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |10/25/2010 10:15 AM                                                                                                                               |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject:   |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |[sca-j] NEW ISSUE: Resolution of Issue 201 is insufficient                                                                                        |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|

Target: CAA Sepc CD04-Rev2

Description:  Issue 201 expanded the definition of @Remotable to have
@Target(TYPE,FIELD,PARAMETER) - FIELD and PARAMETER were added.  This is
insufficient since JCA90053 states: The @Remotable annotation is valid only
on a Java interface, a Java class, a field, a setter method, or a
constructor parameter.  It MUST NOT appear anywhere else. and The POJO
specs states (lines 532-534 of CD02-rev2)

remotable attribute of <interface.java> child element is omitted unless the
interface class has no @Remotable annotation and there is a @Remotable
annotation on the field, setter method or constructor parameter, in which
case the <interface.java> element has remotable="true"

and (lines 600-605 of CD02-rev2)

An unannotated field or setter method is a reference if:
·        its type is an interface annotated with @Remotable
·        its type is an array where the element type of the array is an
interface annotated with @Remotable
·        its type is a java.util.Collection where the parameterized type of
the Collection or its member type is an interface annotated with @Remotable

Proposal: change the @Target fro @Remotable to : @Target
(TYPE,METHOD,FIELD,PARAMETER)

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of
Excellence Application Integration Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: