The product was no longer supporting default values in the mappings from ESB to jBPM variables. A configuration option has been added for supporting legacy default values.
Description of problem:
Customer noticed we no longer allow 'default' values in esbToBpmVars. They are moving from SOA-P 4.x to 5.x and require this functionality.
Tom Cunningham <firstname.lastname@example.org> updated the status of jira JBESB-3902 to Resolved
Tom Cunningham <email@example.com> updated the status of jira JBESB-3902 to Closed
SOA-P now log WARN for unitialized variable as mentioned in support case. Unfortuantely the behaviours is same regardless of
<property name="org.jboss.soa.esb.legacy.bpmvars" value="true"/>
setting. It means that it deviates from 5.3 behaviour and breaks backward compatibility.
I grepped the code for a call of Configuration.getLegacyEsbToBpmParams and there is none.
Talked to Jiri about this on Friday - the WARN is related to another issue which came out of the same case. getLegacyEsbToBpmParams() is called within Configuration itself, and then stored in a KeyValuePair - which is checked. I see the defaults added in the debugger when I set the property.
Verified in CR1 - jbossesb-propertis switch works as advertised and the variable in question is stored in ReplyTo EPR