Thank you very much for the contribution, both solutions worked.
in the end I did was change the line that You mentioned earlier,
concurrentRoot = execution.getParent (); by concurrentRoot = execution;
and it worked perfectly
Thank you very much ;)
Greetings
View the original post :
I just post as a incident. with the test case.
Greetings.
Sebatian
https://jira.jboss.org/jira/browse/JBPM-2648
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4266271#4266271
Reply to the post :
Hi Sebastian,
You found a bug there. It took sometime to understand why is it behaving
that way. I think the problem is there in ForkActivity class. Actually the
following things happen in sequence transition from one Fork node to any other
node.
1. Create child execution for each
Thank you very much for your help, I have already reported the bug.
You think of any alternative for the management of the Fork? because I need to
shoot 2 tasks,and one of the optional, which is not controlled at the end.
but without a Fork not how.
here ther is an example but not working
I
Here is the link of the Bug report.
https://jira.jboss.org/jira/browse/JBPM-2650
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4266384#4266384
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4266384
We can use our understanding about the bug to have a hack for the time being.
We see task1 twice because the transition to task1 is the default transition of
the fork node. To stop task1 from appearing twice we need to make sure that it
is not the default transition. Instead we can add a dummy
Sebastian,
So far I understand, you have some flow like this:
| process name=ForumFlow2 xmlns=http://jbpm.org/4.0/jpdl;
|start g=146,26,48,48 name=start1
| transition g=-43,-18 name=to fork1 to=fork1/
|/start
|fork g=148,100,48,48 name=fork1
| transition
I understand your idea, but i think that is not my situation.
I am attaching an example.
|
| process name=a xmlns=http://jbpm.org/4.0/jpdl;
|
|start g=5,129,48,48 name=start1
| transition to=fork1/
|/start
|end g=957,121,48,48 name=end1/
|
|task
I attach a test case for the situation described above.
Greetings and thanks for the support so far.
Sebatian
| package org.jbpm.examples.task.swimlane;
|
| import java.util.List;
|
| import org.jbpm.api.task.Task;
| import org.jbpm.test.JbpmTestCase;
|
| /**
| * @author
Contrary to what you think and wrote in the jira issue, the unit test is *very*
important in this case. You seem to be using jBPM in a non standard way by
repeating tasks. I'm not saying this is not something that is impossible, but
the way you do it might be very important.
View the original
10 matches
Mail list logo
