[cdi-dev] [JBoss JIRA] Issue Comment Edited: (CDI-44) Clarify that interceptors must be implemented using subclassing, and clarify the behaviour of self-invocation

Marius Bogoevici (JIRA) jira-events at lists.jboss.org
Tue May 24 17:57:01 EDT 2011


    [ https://issues.jboss.org/browse/CDI-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604088#comment-12604088 ] 

Marius Bogoevici edited comment on CDI-44 at 5/24/11 5:55 PM:
--------------------------------------------------------------

1. Use the same list of behavioural criteria as CDI-74 (which was created to cover interception)

2. Describe correct behaviour on self-invocation - and what is the effect of using proxies

      was (Author: marius.bogoevici):
    1. Use the same list of behavioural criteria as CDI-74 (which was created to cover interception)

2. Described self-invocation - when using a proxy
  
> 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: Clarification
>          Components: Interceptors
>    Affects Versions: 1.0
>            Reporter: Stuart Douglas
>            Assignee: Marius Bogoevici
>             Fix For: 1.1 (Proposed)
>
>
> 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

        


More information about the cdi-dev mailing list