This content has been marked as final. Show 4 replies
JBPM job that is created by esb JBpmCallbackService puts output variables from that sample esb service to the scope of root token as well, and not only to the scope of child token.
That is correct, they are currently accessible to all tokens within the process.
I do not understand why there are these lines in org.jboss.soa.esb.services.jbpm.cmd.AsyncProcessSignal.AsyncSignalAction
So that they can be made available to all tokens within the process.
When I delete these lines, I achieve desired (from my point of view) behaviour, not to put output variables to the scope of root token.
Adding a scope for this would be a good idea.
Shall I create feature request? I would appreciate that possibility.
Sorry, I am too quick.