Bug 777774 (SOA-290)

Summary: It is not possible to define variable mapping in jBPM process editor
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Jiri Pechanec <jpechane>
Component: Tooling, JBossESB, JBPM - within SOAAssignee: Tom Baeyens <mail>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 Beta 1CC: kejohnso
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-290
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
FC7/Eclipse Europa/jPDL Designer 3.1.0.SP1
Last Closed: 2011-12-05 18:40:47 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jiri Pechanec 2008-01-08 09:26:32 UTC
Date of First Response: 2008-01-09 11:33:06
project_key: SOA

It is not possible to edit XML content of bpmToEsbVars and esbToBpmVars elements.
This now requires to edit process definition twice - once in graphical designer and second time in text editor to define mapping. This is very inconveniet for user as he frequently lose process arrangement as it is rearranged after this modification.

1) I do not know if the jPDL designer supports editation of nested XML element
2) If he supports it then we should find out if this is problem of only one platform or general deficiency

Comment 1 Mark Little 2008-01-09 16:33:06 UTC
This is a feature request. Moving to 4.3.

Comment 2 Thomas Diesler 2008-07-23 07:44:42 UTC
Revisit Jira assignments. This issue should be assigned again by 28-Aug-2008 

Comment 3 Thomas Diesler 2008-08-11 12:32:59 UTC
TomB is the owner of SOA issues related to the jBPM3 code base

Comment 4 Thomas Diesler 2009-03-10 09:41:02 UTC
Tom, could you please reassign appropriately.

Comment 5 trev 2009-05-22 11:01:19 UTC
Link: Added: This issue depends JBPM-2274


Comment 6 nwallace 2010-01-15 15:01:47 UTC
From Tom
"out of scope.  we don't plan to fix that."

Comment 7 Ken Johnson 2011-12-05 18:40:34 UTC
Closing per defect triage 5-Dec-2011.  
Out of date or no plan to fix.  If this impacts active users, reopen as necessary.