Indeed, I'd rather use the straight-forward syntax, you're right about that.
Doesn't the object become a process variable by using the mapping in ESB?
As follows (thursday already...?):
<property name="esb-to-jbpm">
| <!-- esb-name maps to getBody().get("eVar1") -->
| <variables>
| <variable esb-name="some_object" jbpm-name="jbpm_object" />
| </variables>
| </property>
Meaning the process 'should' have acces to the 'jbpm_object'-variable?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083929#4083929
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083929
>> Ignore petia's example since that also uses a processvariable and just another (imo less wanted) syntax.
That is, of course, unless it works! ;-)
I have a vague memory of running into the same problem and using Petia's workaround early this year., when I was just starting with JBPM. Unfortunately, I don't remember anything useful, like what the underlying problem was, except that as you'd guess, it had to do with variable resolution.
-Ed Staub
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083927#4083927
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083927
