You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2010/11/30 18:00:18 UTC

[jira] Closed: (OPENEJB-1409) Callback overriding adjusted for compliance

     [ https://issues.apache.org/jira/browse/OPENEJB-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Blevins closed OPENEJB-1409.
----------------------------------

    Resolution: Fixed

> Callback overriding adjusted for compliance
> -------------------------------------------
>
>                 Key: OPENEJB-1409
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1409
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: deployment
>            Reporter: David Blevins
>            Assignee: David Blevins
>             Fix For: 3.2
>
>
> OpenEJB had been treating the existence of any <post-construct>,  <pre-destroy>, <around-invoke>, <around-timeout>, <post-activate>,  or <pre-passivate> elements as the definitive list for the respective annotation.  Thus it was possible to remove or change callbacks via xml.  The specification and TCK require that it is only possible to add callbacks via xml, not remove or change them.
> The relevant section from the Interceptors spec document is the following:
> "At most one method of a given interceptor class can be designated as
> an around-invoke method, an around-timeout method, a post-construct
> method, or pre-destroy method, regardless of whether the deployment
> descriptor is used to define interceptors or whether some combination
> of annotations and deployment descriptor elements is used."
> The previous logic, which overrides, can be re-enabled via setting "openejb.callbacks.override" to "true"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.