[jboss-user] [JBoss jBPM] - Re: signaling to a forked sibling
do-not-reply at jboss.com
Fri Sep 12 14:37:06 EDT 2008
yikes... hmm... I would solve it a completely different way I think. More datadriven.
Why not make I1,I2 and I3 variables. Have two states. O1 and O2, each with a decision under them. Each decision has two outcomes, one back to the state and one to a next state. Each time one of the variables get's updated, you signal both states which then go to the decision and each decision checks the values of the variables and decides which transition to take. These decisions can be in java, drools, script or....
One other solution is to just have two states with one outcome (go-further) and put the decisions AND signalling of states in drools. You can decide there which of the states to signal.
Hope I gave you some more info..... either way.... if you could (as you promised to do from now on ;-) ) make this in a unit test, please post it. We need more of these examples.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176235#4176235
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176235
More information about the jboss-user