-
1. Re: Why does my Fork end 3 times instead of 2 (in jBPM 4.3)?
swiderski.maciej Apr 29, 2010 9:32 AM (in response to jody4711)Hi,
I really can't understand why you modeled your process that way. It makes is so complex and gives a lot of confusion with fork and joins. For instance why you have two joins for one fork?
Fork1 ends up in join3 and join2.
What's even more weird, what is the purpose of next fork - fork2?!
/Maciej
-
2. Re: Why does my Fork end 3 times instead of 2 (in jBPM 4.3)?
rebody Apr 29, 2010 10:54 PM (in response to jody4711)Hi Johan,
This is caused by nested fork. And it has already be fixed in the jBPM 4.4-SNAPSHOT. You can see the issue in JIRA been marked as resolved.
https://jira.jboss.org/jira/browse/JBPM-2648
By the way, your xml is totally weired. I don't understand why you used fork/join like this. the join3 looks like useless
-
3. Re: Why does my Fork end 3 times instead of 2 (in jBPM 4.3)?
jody4711 Apr 30, 2010 6:58 AM (in response to rebody)Hi guys,
You are right that my process looks weird. It is because I took a part of a bigger process, and made a test case out of it. Join3 that is followed by Fork2 was inserted because I suspected every fork must be followed by a join, and not another fork. Sadly it didn't help much. The simple test case can be rewritten without nested forks, but our real process cannot. So I will check out the 4.4 snapshot and see if that solves my problem. Thanks for your help!
Regards, Johan
-
4. Re: Why does my Fork end 3 times instead of 2 (in jBPM 4.3)?
jody4711 May 6, 2010 8:34 AM (in response to rebody)Hi,
Now, I have tried my process with jBPM 4.4-SNAPSHOT, and it did work. But the company I work for will not go to production with a snap shot release. When will version 4.4 be released? I know the question has been asked before, but is there an estimate?
Regards, Johan
-
5. Re: Why does my Fork end 3 times instead of 2 (in jBPM 4.3)?
rebody May 7, 2010 10:18 PM (in response to jody4711)Hi Johan,
I think Alejandro will make a plan for relase jBPM-4.4 in the near future. If you have any advice, welcome to join our discussion in the developers forum.