Re: [sca-j] NEW ISSUE: Inconsistent rules for the use of @referenceannotation

Appears like unannotated protected fields computed as properties also have
the same problem.  May be it is a good idea to take care of the @Property
annotation too here itself (unless I am missing something!!).

Java Common Annotations and APIs - v1.0 - Sec 1.8.13:
1349 Properties may also be injected via public setter methods even when
the @Property annotation is not
1350 present. However, the @Property annotation must be used in order to
inject a property onto a non-public
1351 field. In the case where there is no @Property annotation, the name of
the property is the same as the
1352 name of the field or setter.

++Vamsi



                                                                           
             David Booz                                                    
             <>                                             
                                                                        To 
             24/04/2008 01:00                    
                                                                        cc 
                                                                           
                                                                   Subject 
                                       [sca-j] NEW ISSUE: Inconsistent     
                                       rules for the use of @reference     
                                       annotation                          
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




TARGET: SCA Java CA&A (WD02) and SCA Java C&I(draft-20070926)

DESCRIPTION:
Java CAA WD02 - Lines 1235-1239:

The problem in this text is that a reference cannot be injected onto a
protected field without
an @Reference annotation, which contradicts the C&I spec.

Java CI draft 20070926 - line 378

which says that a protected field can be a reference.


See also this email:
http://lists.oasis-open.org/archives/sca-j/200804/msg00040.html


PROPOSAL: Adjust the CAA spec to match the C&I spec.



Dave Booz
STSM, SCA and WebSphere Architecture
Co-Chair OASIS SCA-Policy TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093  or  8-295-6093
e-mail:
http://washome.austin.ibm.com/xwiki/bin/view/SCA2Team/WebHome


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php