[
https://issues.jboss.org/browse/CDI-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Muir updated CDI-44:
-------------------------
Affects Version/s: 1.0
> Clarify that interceptors must be implemented using subclassing, and clarify
> the behaviour of self-invocation
> -------------------------------------------------------------------------------------------------------------
>
> Key: CDI-44
> URL: https://issues.jboss.org/browse/CDI-44
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Affects Versions: 1.0
> Reporter: Stuart Douglas
>
> When implementing interception using proxying the behaour of self invocation
> is quite well defined, if a method is invoked on the proxy it is intercepted,
> if it is invoked on the actual bean (usually through self-invocation) it is
> not.
> When implementing interception though sub classing this is much less well
> definied, and the only way to track if an invocation is intercepted or not is
> through a thread local flag. At the moment in weld this is reset when a call
> is made on a client proxy, so if we have an intercepted bean A and a
> SessionScoped bean B and A invokes B when invokes A the second call to A is
> intercepted. If however B is pseudo scoped, then the second invocation is not
> intercepted. The correct behaviour here should be specified by the
> specification.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
