Bug 781288 - ClassCastException when retrieving AgendaEventListener collection
Summary: ClassCastException when retrieving AgendaEventListener collection
Keywords:
Status: CLOSED DUPLICATE of bug 761427
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRE (Expert, Fusion), jBPM 5
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Tomas Schlosser
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-13 07:50 UTC by Tomas Schlosser
Modified: 2012-04-02 13:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-13 07:59:16 UTC
Type: Bug

Attachments (Terms of Use)
Simple reproducer (1.86 KB, application/x-gzip)
2012-01-13 07:50 UTC, Tomas Schlosser 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Tomas Schlosser 2012-01-13 07:50:00 UTC 
Created attachment 555005 [details]
Simple reproducer

Description of problem:
CCE is thrown upon calling ksession.getAgendaEventListeners()

Version-Release number of selected component (if applicable):
BRMS-5.3.0-ER2

How reproducible:
On StatefulKnowledgeSession

Steps to Reproduce:
1. create stateful session
2. call getAgendaEventListeners()
  
Actual results:
Exception in thread "main" java.lang.ClassCastException: org.jbpm.process.instance.ProcessRuntimeImpl$3 cannot be cast to org.drools.event.rule.AgendaEventListener
	at org.drools.impl.StatefulKnowledgeSessionImpl.getAgendaEventListeners(StatefulKnowledgeSessionImpl.java:182)
	at org.jboss.qa.brms.getlisteners.GetListenersTest.main(GetListenersTest.java:26)

Expected results:
list of listeners

Additional info:
It doesn't matter whether:
 - there is any rule or process
 - there are any listeners
Other listeners getters don't cause this error
Comment 1 Tomas Schlosser 2012-01-13 07:59:16 UTC 

*** This bug has been marked as a duplicate of bug 761427 ***
Note You need to log in before you can comment on or make changes to this bug.