Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion
"Re: Design pattern for routing to multiple jBPM processes?" To view the discussion, visit: https://community.jboss.org/message/805552#805552 -------------------------------------------------------------- Looks like a perfect case for correlated process instances - meaning that you can assign business key to process instances that later on can be used to get hold of process instance. That will come in with version 6.0. And in meantime... option 1 has an issue if you consider to use persistence (and I assume you do as there are long running processes). The issue is you cannot simply query for processes in that session as process instance resides in ksession only when it is being currently executed/processed by the engine. As soon as it reaches a safe state it is persisted and removed from ksession to save memory, etc Option 2 is one way to go and you can easily create processes from rules and as you said you need to make sure you retract fact when process completes. HTH -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/805552#805552] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2034]
_______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
