]
Ronald van Kuijk closed JBPM-512.
---------------------------------
Resolution: Out of Date
behaviour changed in 3.1 (or was it 3.2). If something like this is still an issue, create
a new jira item
jBPM incorrectly accumulating variables for child token
-------------------------------------------------------
Key: JBPM-512
URL:
http://jira.jboss.com/jira/browse/JBPM-512
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM 3.0.1, jBPM 3.0.2
Environment: Running jBPM under JBoss 4.0.2, Sun JDK1.5.0_04, Fedora Core 4
Linux, although the problem is not specific to this environment
Reporter: Jim McMaster
Assigned To: Tom Baeyens
I have a process which forks child tokens to handle parts of the processing. Each node in
the process sets a "status" variable to indicate success or failure. Prior to
the fork, a node set a STATUS_SUCCESS, then the children are forked off.
One of the children invokes a node which sets the status to STATUS_FAILURE, and invokes:
Code:
contextInstance.addVariables(variables, childToken)
At this point, the ContextInstance has two entries in TokenVariableMap, one for the
parent and one for the child. Each variable map contains a status variable, but the values
are different.
Later, I invoke:
Code:
contextInstance.getVariables(token)
When the variables come back, the status varable has the value STATUS_SUCCESS. In
TokenVariableMap.collectAllVariables, the code gets all the variables for the child token,
then adds the variables for the parent. This is great, except it does not check to see if
the variable already exists in the HashMap, so the parent value overlays the child's.
It does not make sense fo the parent token's variables to override those of the
child.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: