You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2011/03/23 11:23:05 UTC
[jira] [Created] (OWB-550) duplicated observer methods in case of
@Specializes
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
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
[jira] [Commented] (OWB-550) duplicated observer methods in case of
@Specializes
Posted by "Mark Struberg (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (OWB-550) duplicated observer methods in case of
@Specializes
Posted by "Gerhard Petracek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OWB-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek updated OWB-550:
---------------------------------
Affects Version/s: 1.1.0
> 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
[jira] [Resolved] (OWB-550) duplicated observer methods in case of
@Specializes
Posted by "Mark Struberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OWB-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg resolved OWB-550.
-------------------------------
Resolution: Fixed
Assignee: Mark Struberg (was: Gurkan Erdogdu)
The notification handling is now slightly different than in owb-1.0.
a) we will not send events to disabled beans anymore
b) since in owb-1.1, we also find observer methods in superclasses, the workflow is different anyway
c) we do not search for the most specialized bean anymore. This is imo not needed because of a) and b) in combination
> 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: Mark Struberg
> 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