[
https://issues.apache.org/jira/browse/OWB-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gurkan Erdogdu resolved OWB-165.
--------------------------------
Resolution: Fixed
Sven,
Looks like problem is related with getting instance from context. To run
interceptors, we have always return to proxy instead of actual instance.
Could you verify ?
Thanks again for helping us!
> 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: M3
> Reporter: Sven Linstaedt
> Assignee: Gurkan Erdogdu
> Fix For: M4
>
> 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.
