You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Prasad Kashyap (JIRA)" <ji...@apache.org> on 2007/05/21 19:12:16 UTC
[jira] Created: (OPENEJB-582) Lifecycle interceptor defined on a
superclass breaks the chain
Lifecycle interceptor defined on a superclass breaks the chain
--------------------------------------------------------------
Key: OPENEJB-582
URL: https://issues.apache.org/jira/browse/OPENEJB-582
Project: OpenEJB
Issue Type: Bug
Components: container system
Affects Versions: 3.0
Reporter: Prasad Kashyap
http://www.nabble.com/Multiple-lifecycle-interceptor-callbacks-don%27t-work-tf3436428s2756.html#a9608013
Section 12.4 of the spec says, "Lifecycle callback interceptor methods may be defined on superclasses of the bean class or interceptor classes. However, a given class may not have more than one lifecycle callback interceptor method for the same lifecycle event."
Also Section 12.4.1 says,
• If a bean class has superclasses, any lifecycle callback interceptor methods defined on those superclasses are invoked, most general superclass first.
• The lifecycle callback interceptor method, if any, on the bean class itself is invoked.
My understanding is that for a given lifecycle event, (say PostConstruct), the bean's superclass' @PostConstruct is first called
followed by the bean's @PostConstruct. Am I correct ? If correct, then how can the superclass' @PostConstruct invoke the
InvocationContext.proceed() ?
The method signature of a lifecycle callback method on a bean or it's superclass should be void <METHOD>() .
Where can it get a handle on the InvocationContext object ? How can it proceed down the chain ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OPENEJB-582) Lifecycle interceptor defined on a
superclass breaks the chain
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins reassigned OPENEJB-582:
-------------------------------------
Assignee: Dain Sundstrom
Dain fixed this one.
> Lifecycle interceptor defined on a superclass breaks the chain
> --------------------------------------------------------------
>
> Key: OPENEJB-582
> URL: https://issues.apache.org/jira/browse/OPENEJB-582
> Project: OpenEJB
> Issue Type: Bug
> Components: container system
> Affects Versions: 3.0
> Reporter: Prasad Kashyap
> Assignee: Dain Sundstrom
>
> http://www.nabble.com/Multiple-lifecycle-interceptor-callbacks-don%27t-work-tf3436428s2756.html#a9608013
> Section 12.4 of the spec says, "Lifecycle callback interceptor methods may be defined on superclasses of the bean class or interceptor classes. However, a given class may not have more than one lifecycle callback interceptor method for the same lifecycle event."
> Also Section 12.4.1 says,
> • If a bean class has superclasses, any lifecycle callback interceptor methods defined on those superclasses are invoked, most general superclass first.
> • The lifecycle callback interceptor method, if any, on the bean class itself is invoked.
> My understanding is that for a given lifecycle event, (say PostConstruct), the bean's superclass' @PostConstruct is first called
> followed by the bean's @PostConstruct. Am I correct ? If correct, then how can the superclass' @PostConstruct invoke the
> InvocationContext.proceed() ?
> The method signature of a lifecycle callback method on a bean or it's superclass should be void <METHOD>() .
> Where can it get a handle on the InvocationContext object ? How can it proceed down the chain ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (OPENEJB-582) Lifecycle interceptor defined on a
superclass breaks the chain
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins closed OPENEJB-582.
---------------------------------
Resolution: Fixed
> Lifecycle interceptor defined on a superclass breaks the chain
> --------------------------------------------------------------
>
> Key: OPENEJB-582
> URL: https://issues.apache.org/jira/browse/OPENEJB-582
> Project: OpenEJB
> Issue Type: Bug
> Components: container system
> Affects Versions: 3.0
> Reporter: Prasad Kashyap
> Assignee: Dain Sundstrom
>
> http://www.nabble.com/Multiple-lifecycle-interceptor-callbacks-don%27t-work-tf3436428s2756.html#a9608013
> Section 12.4 of the spec says, "Lifecycle callback interceptor methods may be defined on superclasses of the bean class or interceptor classes. However, a given class may not have more than one lifecycle callback interceptor method for the same lifecycle event."
> Also Section 12.4.1 says,
> • If a bean class has superclasses, any lifecycle callback interceptor methods defined on those superclasses are invoked, most general superclass first.
> • The lifecycle callback interceptor method, if any, on the bean class itself is invoked.
> My understanding is that for a given lifecycle event, (say PostConstruct), the bean's superclass' @PostConstruct is first called
> followed by the bean's @PostConstruct. Am I correct ? If correct, then how can the superclass' @PostConstruct invoke the
> InvocationContext.proceed() ?
> The method signature of a lifecycle callback method on a bean or it's superclass should be void <METHOD>() .
> Where can it get a handle on the InvocationContext object ? How can it proceed down the chain ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.