salaboy wrote: > > Can you give us a use case for that situation? > Sure! The case is one where an asynchronous workitem - that is, one which doesn't call completeWorkItem from within executeWorkItem - creates messages which need to invoke additional business-process behavior. These could be made to invoke secondary processes, but there's a lot of economy in keeping their behavior within the same process - error-handling, external aborting, and monitoring are all a lot simpler.
-Ed -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Flow-handling-multiple-events-of-the-same-kind-tp767773p773510.html Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
