← Prev in month ← Prev in thread
Next in thread → Next in month →

NEW ISSUE: Inconsistent method description for @Init and @Destroyannotations

From
C Vamsi <>
Date
2008-04-28T19:27:40+00:00
ID
Thread
NEW ISSUE: Inconsistent method description for @Init and @Destroyannotations
DESCRIPTION:
Java Common Annotations and APIs v1.0 - Sec 1.2.4 - Line 269:
269 .... Note that only public, no argument methods may be annotated as
lifecycle methods.

Sec 1.8.8. - Lines 1225 to 1227:
1225 The @Destroy annotation type is used to annotate a Java class method
that will be called when the scope
1226 defined for the local service implemented by the class ends. The
method must have a void return value and
1227 no arguments. The annotated method must be public.

Sec 1.8.11 - Lines 1290 to 1293:
1290 The @Init annotation type is used to annotate a Java class method that
is called when the scope defined for
1291 the local service implemented by the class starts. The method must
have a void return value and no
1292 arguments. The annotated method must be public. The annotated method
is called after all property and
1293 reference injection is complete.

REASON: Sec 1.2.4 does not talk about return type of the method whereas
sections 1.8.8. and 1.8.11 say that the method must have a void return
value.

PROPOSAL: Make the method description consistent across these three
sections.  Change line 269 to read the following:
.... Note that only public, no argument methods with a void return type may
be annotated as lifecycle methods.

In lines 1226 and 1291, change "void return value" to "void return type".

See http://lists.oasis-open.org/archives/sca-j/200804/msg00059.html

++Vamsi
← Prev in month ← Prev in thread
Next in thread → Next in month →