[ 
https://issues.apache.org/jira/browse/OWB-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475673#comment-13475673
 ] 

Daniel Sachse commented on OWB-711:
-----------------------------------

Hey guys,

thanks for your effort so far.
To me, the situation regarding scenarios one and three is clearly stated in the 
specification(last paragraph of 4.3):
"When an enabled bean, as defined in Section 5.1.2, “Enabled and disabled 
beans”, specializes a second bean, we can be certain that the second bean is 
never instantiated or called by the container. Even if the second bean defines 
a producer or observer method, the method will never be called."
>From my point of view it would be illegal to call the observer methods from a 
>superclass, if the subclass defines @Specializes althouth observer methods 
>should in general be called.
WDYT?
                
> Specialization does not deactivate Observer methods in parent class
> -------------------------------------------------------------------
>
>                 Key: OWB-711
>                 URL: https://issues.apache.org/jira/browse/OWB-711
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Inheritance, Specialization
>    Affects Versions: 1.1.5
>            Reporter: Daniel Sachse
>            Assignee: Arne Limburg
>              Labels: patch
>             Fix For: 1.1.7
>
>         Attachments: Observer, Alternative, Specialize.patch
>
>
> I found some bugs regarding @Specializes and Observer methods.
> The scenarios:
> @Specializes Bean without overriding Observer-method: Observer gets called
> @Specializes Bean with Overridden Observer-method: Overridden Observer gets 
> called twice
> @Alternative @Specializes Bean without overriding Observer-method: Observer 
> gets called
> @Alternative @Specializes Bean with overridden Observer-method: Overridden 
> Observer gets called twice
> I attached a patch file for the tests which do of course fail at the moment ;)

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

Reply via email to