You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Vamsavardhana Reddy (JIRA)" <tu...@ws.apache.org> on 2008/05/01 17:34:55 UTC
[jira] Updated: (TUSCANY-2272) @Init and @Destroy annotations on a
non-public method
[ https://issues.apache.org/jira/browse/TUSCANY-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vamsavardhana Reddy updated TUSCANY-2272:
-----------------------------------------
Component/s: (was: Java SCA Verification Tests)
> @Init and @Destroy annotations on a non-public method
> ------------------------------------------------------
>
> Key: TUSCANY-2272
> URL: https://issues.apache.org/jira/browse/TUSCANY-2272
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Java Implementation Extension
> Affects Versions: Java-SCA-1.2
> Reporter: Vamsavardhana Reddy
> Assignee: Vamsavardhana Reddy
> Fix For: Java-SCA-Next
>
> Attachments: TUSCANY-2272.patch
>
>
> Java Common Annotations and APIs Specification v1.00 - Sec 1.2.4 - Lines 265 to 269:
> 265 An implementation type may allow component implementations to declare lifecycle methods that are
> 266 called when an implementation is instantiated or the scope is expired. @Init denotes the method to be
> 267 called upon first use of an instance during the lifetime of the scope (except for composite scoped
> 268 implementation marked to eagerly initialize, see Section XXX). @Destroy specifies the method to be called
> 269 when the scope ends. *Note that only public, no argument methods may be annotated as lifecycle methods.*
> Currently @Init and @Destroy annotations on a protected method do not result in an error or a warning whereas these annotations on a private method result in a warning. Should it result in an error in both cases?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.