On 16/09/2013, Sonata <plz.write.to(a)gmail.com&gt; wrote: No, there isn't, and there are good reasons not to add it. If I had this requirement, I'd probably implement a Proxy for KnowledgeBase with the added functionality of maintaining the listeners and doing the required magic when a new session is created from the Knowledge Base. -W

I can't speak for the team, but my reasons are: - The API (even the public one) is already very rich, and extensions should be considered very carefully. - You'd have to have the code for defining the listeners anyway - so why not execute it on each session? - Having a single listener listen to multiple sessions running in parallel is hardly useful, and so your proposal is only good for a sequential succession of sessions. - For the sequentail case: you could easily attach the listener from within a high-priority rule to the session by which it is executed. Note that this is practically identical to having the listeners defined with the knowledge base. -W On 17/09/2013, Sonata <plz.write.to(a)gmail.com&gt; wrote: