[cdi-dev] [JBoss JIRA] (CDI-277) Clarify inheritance behavior of observer methods

Arne Limburg (JIRA) jira-events at lists.jboss.org
Sat Oct 13 11:58:01 EDT 2012


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

Arne Limburg commented on CDI-277:
----------------------------------

On event1 I would expect to be called:
observer1 of BeanA on an instance of BeanB
observer1 of BeanA on an instance of BeanC
observer1 of BeanB on an instance of BeanB
observer1 of BeanC on an instance of BeanC
observer1 of BeanA is NOT called on an instance of BeanA because it is specialized

On event2 I would expect to be called:
observer2 of BeanB on an instance of BeanB
observer2 of BeanC on an instance of BeanC
observer2 of BeanA is NOT called because BeanB and BeanC override it and no instance of BeanA exists, because BeanC specializes it.

On event3 I would expect to be called:
observer3 of BeanB
observer3 of BeanC
observer3 of BeanA is NOT called because BeanA is specialized

On event4 I would expect to be called:
observer4 of BeanB
observer4 of BeanC
observer4 of BeanA is NOT called because BeanA is specialized

wdyt?
                
> Clarify inheritance behavior of observer methods
> ------------------------------------------------
>
>                 Key: CDI-277
>                 URL: https://issues.jboss.org/browse/CDI-277
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>            Reporter: Arne Limburg
>
> Chapter 4.2 of the (1.0) spec misses a bullet point about inheritance of observer methods.
> Either
> - If X declares a non-static observer method x() then Y does inherit this method.
> or
> - If X declares a non-static observer method x() then Y does not inherit this method.
> (This behavior is different to what is defined in the Common Annotations for the Java Platform specification.)
> should be added.
> Don't know, what's right through...

--
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


More information about the cdi-dev mailing list