[
https://issues.apache.org/jira/browse/OWB-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475569#comment-13475569
]
Mark Struberg commented on OWB-711:
-----------------------------------
JBoss Jira is down atm, so an uneducated question:
{quote}
10.2. Observer resolution
An event is delivered to an observer method if:
• The observer method belongs to an enabled bean.
{quote}
In my opinion the following must get clarified:
1.) This bullet clearly disables veto() beans from receiving Observers.
2.) @Alternative has no influence on Observers at all! They do not disable
beans but only affect the resolution process.
3.) A @Specializes class Y must be a subclass of anoter class X. If X defines
an observe rmethod then this is also part of class Y and thus will get called.
4.) Any Reception.ALWAYS Observer method in X will NOT create a contextual
instance of X but _only_ of type Y (as X is not an enabled bean)
What I'm asking me is how one can disable a private observe rmethod in it's
superclass or a static observer method at all ^^ Probably only via Extensions.
> 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
