In order to support common CEP scenarios, the BusinessRulesProcessor action needs an option to automatically control the lifecycle of the stateful knowledge session.
Currently, if using stateful knowledge sessions, you must control when the session is created, reused, and disposed of using message properties. In a CEP scenario, there is no need for this lifecycle nor is it desired.
It would be better to have an option that will automatically create a new session upon receiving the first message and automatically reuse the existing session upon receiving subsequent messages. Dispose would not be needed as Drools automatically manages working memory in stream mode.