[
https://issues.jboss.org/browse/JBESB-3902?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3902:
------------------------------------------------
Jiri Pechanec <jpechane(a)redhat.com> made a comment on [bug
902888|https://bugzilla.redhat.com/show_bug.cgi?id=902888]
SOA-P now log WARN for unitialized variable as mentioned in support case. Unfortuantely
the behaviours is same regardless of
<properties name="bpm">
<property name="org.jboss.soa.esb.legacy.bpmvars"
value="true"/>
</properties>
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.
Restore esbToBpmVars as a command line option
---------------------------------------------
Key: JBESB-3902
URL:
https://issues.jboss.org/browse/JBESB-3902
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.11 CP2
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.11 CP2
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira