Re: [sca-j] ISSUE 41: Proposal

[Simon Nash <NASH@uk.ibm.com>]

This use of MAY in the section 2.2 change
isn't correct in RFC2119 terms.  Mike has already proposed a change
to section 2.2 to correct this.  Taking Mike's proposed words together
with the update to add the "void return type" restriction would
give something like:

"Methods annotated as lifecycle
methods MUST be public with no arguments and a void return type."

    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>

10/07/2008 10:56

To	sca-j@lists.oasis-open.org
cc
Subject	[sca-j] ISSUE 41: Proposal

Ref: sca-javacaa-1.1-spec-WD03.doc
Change the text in the given sections and line range as given below:

Section 2.2 - Line 121:
Note that only public, no-argument methods with a void return type MAY
be
annotated as lifecycle methods.

Section 8.9 - Lines 1184-1186:
The @Destroy annotation is used to denote a Java class method that will
be
called when the scope defined for the local service implemented by the
class ends. The method MUST have a void return type and no arguments. The
annotated method MUST be public.

Section 8.12 - Lines 1257-1260:
The @Init annotation is used to denote a Java class method that is called
when the scope defined for the local service implemented by the class
starts. The method MUST have a void return type and no arguments. The
annotated method MUST be public.  The annotated method is called after
all
property and reference injection is complete.


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to 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