You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Sven Linstaedt (JIRA)" <ji...@apache.org> on 2009/11/14 23:06:39 UTC

[jira] Updated: (OWB-165) Missing bean interception stack during TagHandler expression evaluation

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

Sven Linstaedt updated OWB-165:
-------------------------------

    Attachment: webapp-sources.jar

> Missing bean interception stack during TagHandler expression evaluation
> -----------------------------------------------------------------------
>
>                 Key: OWB-165
>                 URL: https://issues.apache.org/jira/browse/OWB-165
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Interceptor and Decorators
>    Affects Versions: 1.0.0
>            Reporter: Sven Linstaedt
>            Assignee: Gurkan Erdogdu
>         Attachments: webapp-sources.jar, webapp.war
>
>
> Given a JSF controller bean, which should be intercepted by in simple interceptor. If one of it's methods is invoked via EL using a MethodExpression bound to a commandButton, the controller bean is called without interception stack (meaning: the interceptor is not called). If I invoke the same method from within another controller bean programmatically, the interception stack is in place and the interceptor is called.
> As far as I figured this issue out, the problem is due to the phase, when the bean is created. If you remove the <c:if test="#{testController.show}"> in the example, the interceptor is called.
> http://localhost:8080/interceptor.xhtml

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