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 <[email protected]> wrote: > laune wrote >> No, there isn't, and there are good reasons not to add it. > > Thanks for letting me know. It would be great if you can also let us know > the team's reasons behind this decision. > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Any-way-to-make-an-AgendaEventListener-always-attach-to-any-ksession-from-the-same-kbase-tp4025964p4025988.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
