[
https://jira.jboss.org/jira/browse/JBPM-2581?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2581:
----------------------------------------
Ok,after 'fixing' the weird testcase (it contained a lot of wrong assumptions
about what was the first task etc) Suggestion: Look at what the JBPMTestcase provides for
you... LOTS of great additional methods e.g. to be sure you get task1 and not by accident
task2 when doing tasklist.get(0).... do this by using getTask(tasklist,
"task1")....
But the good news is, even this 'weird' case works up to what the poster had in
his test.. Heck, I gave it a try and it even works further... GREAT JOB JBPM...
I'll make a test for the normal one now...
Problems with nested Forks
---------------------------
Key: JBPM-2581
URL:
https://jira.jboss.org/jira/browse/JBPM-2581
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.0
Environment: Windows xp, Eclipse galileo and jbpm integred with spring and
hibernate.
Reporter: Sebastian Castellanos
Assignee: Alejandro Guizar
Fix For: jBPM 4.4
Attachments: a.jpdl.xml, TestForkAndJoin.java, testForkAndJoin.jpdl.xml
Original Estimate: 3 days
Remaining Estimate: 3 days
First off, I apologize for not having made the unit tests, but do not have time at the
moment and I think it is a conceptual problem and a unit test would not provide much.
I am integrating jBPM version 4.1 and it proves there too.
The situation is this:
When launched a nested Fork1 another in the second Fork repeats one of its tasks.
In the xml it becomes clear what the situation.
Maybe it is a conceptual issue, and I who is mishandled.
I would be grateful if I can help, as I searched in different places this situation and
found no alternative but to post it here.
Greetings.
Sebastian.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira