[
https://issues.apache.org/jira/browse/OWB-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634981#comment-13634981
]
Arne Limburg commented on OWB-828:
----------------------------------
About testing the factories: We would have to inpect the stacktrace during the
test
Not nice, but maybe a working solution.
> OwbInterceptProxy wrapping an OwbInterceptProxy
> -----------------------------------------------
>
> Key: OWB-828
> URL: https://issues.apache.org/jira/browse/OWB-828
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Interceptor and Decorators
> Affects Versions: 1.2.0
> Reporter: Gerhard Petracek
> Assignee: Arne Limburg
> Priority: Critical
> Attachments: OWB-828_2.patch, OWB-828.patch
>
>
> it looks like a concurrency issue with interceptor-proxies since it doesn't
> happen in all cases.
> normal ( /working):
> LifecycleInterceptorInvocationContext#proceed L95
> //reflection calls
> MyReqScopedBean#postConstruct
> MyAppScopedBean$OwbNormalScopeProxy0#myMethod
> MyAppScopedBean$OwbInterceptProxy0#myMethod
> MyAppScopedBean#myMethod
> [injection points ok]
> not working:
> LifecycleInterceptorInvocationContext#proceed L95
> //reflection calls
> MyReqScopedBean#postConstruct
> MyAppScopedBean$OwbNormalScopeProxy0#myMethod
> MyAppScopedBean$OwbInterceptProxy0#myMethod
> MyAppScopedBean$OwbInterceptProxy0#myMethod
> [injection points are null]
> there is only one instance of $$OwbInterceptProxy0 for the bean in question,
> but the final method call gets executed by the proxy itself instead of its
> proxied instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
