Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 902888

Summary: Please allow user to specify defaults in esbToBpmVars
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Rick Wagner <rwagner>
Component: JBossESBAssignee: tcunning
Status: CLOSED UPSTREAM QA Contact: Jiri Pechanec <jpechane>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.3.0 GACC: jpechane, ldimaggi, soa-p-jira
Target Milestone: CR1   
Target Release: 5.3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
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.
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:27:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rick Wagner 2013-01-22 16:02:00 UTC
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.

Comment 1 JBoss JIRA Server 2013-02-12 21:51:24 UTC
Tom Cunningham <tcunning> updated the status of jira JBESB-3902 to Resolved

Comment 2 JBoss JIRA Server 2013-02-12 21:51:38 UTC
Tom Cunningham <tcunning> updated the status of jira JBESB-3902 to Closed

Comment 3 Jiri Pechanec 2013-02-15 09:38:40 UTC
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.

Comment 4 tcunning 2013-02-15 16:39:25 UTC
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.

Comment 5 Jiri Pechanec 2013-02-18 06:42:00 UTC
Verified in CR1 - jbossesb-propertis switch works as advertised and the variable in question is stored in ReplyTo EPR

Comment 11 Red Hat Bugzilla 2025-02-10 03:27:20 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.