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

Jozef Hartinger (JIRA) jira-events at lists.jboss.org
Mon Oct 15 03:38:01 EDT 2012


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

Jozef Hartinger commented on CDI-277:
-------------------------------------

{quote} 1.) This bullet clearly disables veto() beans from receiving Observers, right? {quote}

A vetoed bean is definitely not an enabled bean so this is clear IMHO.


{quote}2.) @Alternative has no influence on Observers at all! They do not disable beans but only affect the resolution process.{quote}

{quote}A bean is said to be enabled if:  it is not an alternative, or it is a selected alternative of at least one bean archive.{quote}

{quote}An event is delivered to an observer method if:  The observer method belongs to an enabled bean.{quote}

So from there I would say that @Alternatives do have influence on observers.



                
> 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