Bug 974945 - BPM Component ignores output mapping
BPM Component ignores output mapping
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: SwitchYard (Show other bugs)
6.0.0 GA
Unspecified Unspecified
unspecified Severity high
: DR6
: 6.0.0
Assigned To: Keith Babo
Jiri Pechanec
Depends On:
  Show dependency treegraph
Reported: 2013-06-17 04:32 EDT by Jiri Pechanec
Modified: 2014-06-16 19:52 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In previous versions, users would encounter problems with mapping. Global mappings were not inserted as global variables in the knowledge runtime. This would result in them being ignored by the BPM component. This has been fixed in the current version.
Story Points: ---
Clone Of:
Last Closed: 2014-02-06 10:26:47 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker SWITCHYARD-1382 Critical Closed Rules and BPM Variable Handling Fixes 2014-06-16 19:51:59 EDT

  None (edit)
Description Jiri Pechanec 2013-06-17 04:32:18 EDT
I'd expect I can use a similar mapping as I can use for input mapping, so for example for input I set

Process/in = message.content

But if I try it for output mapping like this

Process/out = message.content then it does not work. It is hardcoded in BPMExchangeHandler.handleOutput() that I need to use 'contentOutput' parameter to set a message content based on a BPM variable and the other variables are propagated automatically as context properties.

As tooling by default proposes message.content as a default for output mapping and documentation does not speak about magic names I suppose this is a bug.
Comment 1 Jiri Pechanec 2013-06-17 04:47:59 EDT
Also please look at Actions tab for BPM Component, tables Input and Output, column names Expression and Variable are VERY confusing as they means something completely different in these two contexts.
Comment 2 Keith Babo 2013-06-17 07:13:59 EDT
This is fixed in https://issues.jboss.org/browse/SWITCHYARD-1382 for 1.0.  This change should be in Alpha 2.
Comment 6 Jiri Pechanec 2013-10-21 08:18:13 EDT
Verified in ER6
Comment 7 JBoss JIRA Server 2014-06-16 19:52:00 EDT
Keith Babo <kbabo@redhat.com> updated the status of jira SWITCHYARD-1382 to Closed

Note You need to log in before you can comment on or make changes to this bug.