[jboss-jira] [JBoss JIRA] (JBRULES-3666) kbase holds multiple KnowledgeBaseEventListenerWrapper instances when adding the same KnowledgeBaseEventListener multiple times

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on JBRULES-3666:
--------------------------------------------------

Toshiya Kobayashi <tkobayas at redhat.com> made a comment on [bug 958394|https://bugzilla.redhat.com/show_bug.cgi?id=958394]

+++ This bug was initially created as a clone of Bug #868913 +++

Description of problem:

Platform BZ for JBRULES-3666

Steps to Reproduce:
Actual results:
Expected results:

I think the unit test which is sent as the pull request would be fine.
https://github.com/droolsjbpm/drools/pull/153

--- Additional comment from JBoss JIRA Server on 2012-11-01 08:16:54 EDT ---

Mario Fusco <mario.fusco at gmail.com> updated the status of jira JBRULES-3666 to Resolved
                
> kbase holds multiple KnowledgeBaseEventListenerWrapper instances when adding the same KnowledgeBaseEventListener multiple times
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-3666
>                 URL: https://issues.jboss.org/browse/JBRULES-3666
>             Project: JBRULES
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-core
>    Affects Versions: 5.5.0.Beta1
>            Reporter: Toshiya Kobayashi
>            Assignee: Mario Fusco
>             Fix For: 5.5.0.Final
>
>
> When you add the same KnowledgeBaseEventListener to kbase twice, kbase holds both KnowledgeBaseEventListenerWrapper instances. I'm not 100% sure if this is a bug but I guess KnowledgeBaseEventListenerWrapper should implement equals() method like StatefulKnowledgeSessionImpl$AgendaEventListenerWrapper.

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