[
https://jira.jboss.org/jira/browse/JBESB-2159?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2159:
-------------------------------------
The default scope of the variables, if unspecified, was intended to be process scope.
This issue fixes a code change which treated an unspecified scope as equivalent to a local
scope.
The variables from services started in forked branches are lsot
---------------------------------------------------------------
Key: JBESB-2159
URL:
https://jira.jboss.org/jira/browse/JBESB-2159
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP3
Environment: IR1 on FC8
Reporter: Jiri Pechanec
Assignee: Tom Fennelly
Priority: Critical
Fix For: 4.2.1 CP4
The bpm_orchestartion2 qs provides different results in 4.2 and 4.3 versions. The problem
is the the message modifications done in forked branches are not propagated back to the
process. There are two possible explanations for this behaviour
1) The ProcessInstance.setVaribale method in jBPM does not set variable on root context -
which means that there is bug in jBPM
2) Or behaviour with default configuration has changed
I am attaching modified jboss-esb.xml and process definiton file that stores the service
outcome under different variables in different branches so they are not overwritten in
join node.
You will see that in 4.3 the branch slots are not progpagated after the join node.
--
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