Bug 998850

Summary:	Metadata of messages coming thorough bindings cannot be process by IP
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Jiri Pechanec <jpechane>
Component:	RT Governance	Assignee:	Gary Brown <gbrown>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Pechanec <jpechane>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.0 GA	CC:	soa-p-jira
Target Milestone:	ER2
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-06 15:26:24 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 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