[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-j] @Reference annotation on setter method parameter or the methoditself?
Hi Simon,
If the issue has already been resolved and the TC feels that the proposed
wording is sufficiently clear, I am alright with the adapted resolution and
do not want to reopen the issue. Since the draft
sca-javacaa-1.1-spec-WD-01.doc available at
http://www.oasis-open.org/committees/download.php/27997/sca-javacaa-1.1-spec-WD-01.doc
did not incorporate this change, I thought it would still be possible to
change it. And when it comes to choosing between "sufficiently clear" and
"clear", I would choose "clear", but this is a personal choice :)
++Vamsi
Simon Nash
<NASH@uk.ibm.com>
To
28/04/2008 16:39 sca-j@lists.oasis-open.org
cc
Subject
Re: [sca-j] @Reference annotation
on setter method parameter or the
method itself?
Vamsi,
JAVA-33 is resolved. �Please see the minutes of the sca-j call of April
3. �The proposed wording change in the JIRA was adopted. �The point you are
making was raised (by myself!) when the TC discussed the motion to resolve
the issue. �Other TC members felt that the proposed wording was
sufficiently clear, so I did not press this to a vote. �Are you OK with the
wording that was adopted, or do you want to reopen the issue with a
proposal to change the wording?
� � Simon
Simon C. Nash, IBM Distinguished Engineer
Member of the IBM Academy of Technology
Tel. +44-1962-815156 �Fax +44-1962-818999
C Vamsi
<vamsic007@in.ibm.com>
To
28/04/2008 05:05 Simon Nash/UK/IBM@IBMGB
cc
sca-j@lists.oasis-open.org
Subject
Re: [sca-j] @Reference
annotation on setter method
parameter or the method
itself?
Hi Simon,
Thank you for pointing to JAVA-33. �I failed to locate that issue since
"Java Common Annotations and APIs specification" is not marked as the
component affected by this issue. �I don't think JAVA-33 is resolved yet as
I notice that the text in section 2.1.4 of v1.1 draft does not reflect the
resolution and even the status at http://www.osoa.org/jira/browse/JAVA-33
is still shown as "New". �Though the current proposal for JAVA-33 changes
"setter method parameter" to "setter method", it is not the setter method
but the parameter to the setter method that is typed by the service
interface. �I am alright if my proposed resolution gets considered under
JAVA-33 itself.
++Vamsi
� � � � � � Simon Nash
� � � � � � <NASH@uk.ibm.com>
� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �To
� � � � � � 28/04/2008 03:00 � � � � �sca-j@lists.oasis-open.org
� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �cc
� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � Subject
� � � � � � � � � � � � � � � � � � � Re: [sca-j] @Reference annotation
� � � � � � � � � � � � � � � � � � � on setter method parameter or the
� � � � � � � � � � � � � � � � � � � method itself?
Vamsi,
This appears to be a duplicate of JAVA-33. �Were you intending to reopen
that issue (which would require a 2/3 majority), or are you OK with the
change made to this text by the resolution to JAVA-33?
� � Simon
Simon C. Nash, IBM Distinguished Engineer
Member of the IBM Academy of Technology
Tel. +44-1962-815156 �Fax +44-1962-818999
C Vamsi
<vamsic007@in.ibm.com>
� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �To
26/04/2008 09:51 � � � � � � � � � � � � � �sca-j@lists.oasis-open.org
� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �cc
� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � Subject
� � � � � � � � � � � � � � � � � � � � � � [sca-j] @Reference annotation
� � � � � � � � � � � � � � � � � � � � � � on setter method parameter or
� � � � � � � � � � � � � � � � � � � � � � the method itself?
DESCRIPTION:
Java Common Annotations and APIs Specification v1.00 - Sec 1.2.2 - Lines
245 to 246:
245 Accessing a service using reference injection is done by defining a
field, a setter method parameter, or a
246 constructor parameter typed by the service interface and annotated with
an @Reference annotation.
From the above it could be interpreted that the parameter to the setter
method can be annotated with @Reference whereas section 1.8.14 does not
talk about or give an example where a parameter to the setter method is
annotated with @Reference, but mentions that the setter method itself (not
the input parameter) should be annotated with @Reference.
PROPOSAL: Change lines 245 and 246 to read the following:
Accessing a service using reference injection is done by defining a field,
a setter method with input parameter typed by the service interface, or a
constructor parameter typed by the service interface and annotated with an
@Reference annotation.
++Vamsi
---------------------------------------------------------------------
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
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
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]