The idea is to run multiple independent sub flows. Each of the sub flows requires approximately 2 minutes to complete, so parallel processing is required. Once all the sub flows have completed their tasks is necessary to collect all the results and process them. This implies that the workflow should not end until it collects all information submitted by the sub flows.
For now, I think to create, with JMS, a queue in jboss receive the name of each sub flow, create your own KnowledgeBase run each subflow as a separate workflow and delivers the results. Finally, some components will take all the results (from a database of another jms queue and process and again another component start another workflow to process all results.
PEDRO BUITRAGO
Bogotá, Colombia2010/4/22 Mauricio Salatino <salaboy@gmail.com>
can you describe a little bit your use case?
I'm not sure about what you want to achieve.
2010/4/21 Pedro Maria Buitrago Mantilla <pmbtgun@gmail.com>
In general, I meet that for resolve the topic of multithreading it's required to implement another thread over a work item.
How does the asynchronic task can modified a variable of Knowledgebase?
Can you give me an example?
Pedro Buitrago
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users