-
15. Re: ESB & jBPM variables integration problem
Alright. In order to sink my teeth somewhat deeper into it, I had a question about the functionality. I'm using a jbpmTokenId in the message, like some examples do, and the variable remains part of the message throughout the whole ordeal. But when I add a different variable to the body, say 'containerID', it gets lost again in the next step. (also when using the jBPM/ESB mappings for this variable-name)
Are there strict rules concerning the usage of the name for variables that are set in the message's body? -
16. Re: ESB & jBPM variables integration problem
There are no rules. Just some names are used 'internally' and carried over between contexts. So for your own variables you need to specify them in the mapping.
On the CP branch I actually removed some of this behavior and all the interaction will be asynchronous, and I'm writing a guide now, since we don't have one yet.
Helpt dat?
--Kurt -
17. Re: ESB & jBPM variables integration problem
Helpt zeker.
I expected that was what was going on, just making sure. -
18. Re: ESB & jBPM variables integration problem
Hey, a last update.
Though the problem has been solved, I am uncertain wether or not it is a bug.
I removed mappings I did not use in certain portions of the code once the content was processed, ie:<property name="object-paths"> <object-path esb="BODY_CONTENT" bpm="theBody" /> </property>
Once I processed the body content and serialized it into an object, attached to the message, I only mapped this object and nothing else. This works fine. Earlier, I also mapped the BODY_CONTENT and contentsAsString along with the object but unfortunately have no explanation why that should matter.