[
https://issues.apache.org/jira/browse/OWB-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010163#comment-13010163
]
Mark Struberg commented on OWB-550:
-----------------------------------
hehe, actually this bug already did exist in owb-1.0.0, but in the old version,
we did not find @Observes method in base classes ;)
Thus previously we only had 1 ObserverMethod, but for the wrong BeanA!
Now we correctly find the ObserverMethod in BeanB's class hierarchy, so we just
need to get rid of the ObserverMethod in the inactive bean (BeanA is
overwritten by the @Specialized BeanB)..
> duplicated observer methods in case of @Specializes
> ---------------------------------------------------
>
> Key: OWB-550
> URL: https://issues.apache.org/jira/browse/OWB-550
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Events
> Affects Versions: 1.1.0
> Reporter: Gerhard Petracek
> Assignee: Gurkan Erdogdu
> Priority: Blocker
> Fix For: 1.1.0
>
>
> this issue is new in the current snapshot (with owb 1.0.0 it works correctly)
> - therefore it's a blocker.
> if bean 'a' contains an observer method and bean 'b' is a specialization of
> bean 'a' (without observer method), the current snapshot triggers the
> observer method twice.
> (the list in NotificationManager#fireEvent contains an additional entry)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
