You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Gurkan Erdogdu (JIRA)" <ji...@apache.org> on 2010/06/02 21:00:48 UTC
[jira] Updated: (OWB-306) overrridden @AroundInvoke and lifecycle
interceptors are still run
[ https://issues.apache.org/jira/browse/OWB-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gurkan Erdogdu updated OWB-306:
-------------------------------
Fix Version/s: 1.0.0-CR2
(was: 1.0.0-CR1)
Affects Version/s: 1.0.0-CR1
(was: M3)
> overrridden @AroundInvoke and lifecycle interceptors are still run
> ------------------------------------------------------------------
>
> Key: OWB-306
> URL: https://issues.apache.org/jira/browse/OWB-306
> Project: OpenWebBeans
> Issue Type: Bug
> Affects Versions: 1.0.0-CR1
> Reporter: Eric Covener
> Assignee: Eric Covener
> Fix For: 1.0.0-CR2
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> Interceptor spec says:
> ---
> If an around-invoke method is overridden by another method (regardless of whether that method is itself an around-invoke method), it will not be invoked.
> If a lifecycle callback interceptor method is overridden by another method (regardless of whether that
> method is itself a lifecycle callback interceptor method (of the same or different type)), it will not be
> invoked.
> ---
> I don't have a fix for this issue, but it is at least conceptually pretty easy to grok.
> It seems that we can't just check the stack or even all enabled interceptors
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.