-
1. Re: Splitting Tasks Dynamically then Merging ... can it be d
salaboy21 Aug 25, 2008 12:04 PM (in response to kasim)I don't fully understand your question but you must look at this wiki to search guidance.
http://wiki.jboss.org/wiki/MultiChoiceForkAH -
2. Re: Splitting Tasks Dynamically then Merging ... can it be d
kasim Aug 25, 2008 12:14 PM (in response to kasim)"salaboy21" wrote:
I don't fully understand your question but you must look at this wiki to search guidance.
http://wiki.jboss.org/wiki/MultiChoiceForkAH
Thanks for the link.
I have read quite a bit of jbpm before .... its just a lower specific.
Part of my problem is i want to be able to dynamically throttle the amount of "workers"
This image is kind of the system i am going for -
http://static.springframework.org/spring-batch/images/partitioned.png -
3. Re: Splitting Tasks Dynamically then Merging ... can it be d
salaboy21 Aug 25, 2008 12:20 PM (in response to kasim)yeap... that's exactly that i understand.. you can do it with this
http://wiki.jboss.org/wiki/MultiChoiceForkAH
This make dinamic paths that could have any number of tasks, and the number of paths can be calculed at runtime.
In adition to this, you could use JMS to the actual work, but when the work is done, is informed to the process.
That makes sense to you?
I hope it helps -
4. Re: Splitting Tasks Dynamically then Merging ... can it be d
kukeltje Aug 26, 2008 6:21 AM (in response to kasim)yes, and as Salaboy says, there is no real throtteling. They are all created at once. But if you make the work in them async (you should!!) then the jobscheduler can be used to throttle them, or the enterprise scheduler.
You could also put messages in your own queue and do some more advanced throtteling over there. But combining this with the MultiChoiceForkAH is certainly the way to go. -
5. Re: Splitting Tasks Dynamically then Merging ... can it be d
kasim Sep 3, 2008 11:49 AM (in response to kasim)
I am sorry i am still not sure i understand how it knows when its done.
If you put it in a JMS queue, the MDB has to pick it up. So do you just have in the mdb a forward to the next jbpm then?
Sorry my jbpm knowledge is a bit limited -
6. Re: Splitting Tasks Dynamically then Merging ... can it be d
kukeltje Sep 3, 2008 12:41 PM (in response to kasim)lot of 'it(s)' in here, all different ones I think, so I have no real clue what you do not understand. But let me try
I am sorry i am still not sure i understand how it knows when its done.
if 'it' is the action, that is part of the async functionality. jBPM keeps track of what action belongs to what node. If 'it' is your own throttling mechanism, you have to keep track of what is done yourself (e.g. token-id's in the messages)If you put it in a JMS queue, the MDB has to pick it up. So do you just have in the mdb a forward to the next jbpm then?
Kind of, just not to the 'next' jBPM (node you probably mean) but signal that a certain token is done. That is what I meant by keeping the token-id above