Bug 998850 - Metadata of messages coming thorough bindings cannot be process by IP
Summary: Metadata of messages coming thorough bindings cannot be process by IP
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: RT Governance
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER2
: 6.0.0
Assignee: Gary Brown
QA Contact: Jiri Pechanec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-20 08:30 UTC by Jiri Pechanec
Modified: 2014-07-02 09:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-06 15:26:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RTGOV-256 0 Major Closed Headers not reported for switchyard events 2014-07-02 09:18:33 UTC

Description Jiri Pechanec 2013-08-20 08:30:53 UTC 
Certain transports can deliver messages that have associated metadata related to business transaction/conversation - e.g.
  - JMS headers - JMS correlation id
  - SOAP - WS-Addressing

These metadata can be get into SY by using context mapper that allows to store them as exchange properties. Unfortunately when admin would like to turn those metadata into RTGov properties or context (for example for conversation spanning multiple systems) it is not possible as IP will receive only message body but not exchange properties.
Comment 1 Jiri Pechanec 2013-09-17 11:58:16 UTC 
Verified in ER2
Comment 5 JBoss JIRA Server 2014-07-02 09:18:34 UTC 
Gary Brown <gary> updated the status of jira RTGOV-256 to Closed
Note You need to log in before you can comment on or make changes to this bug.