Bug 1133996 - Provide propagating of headers/properties in all components
Summary: Provide propagating of headers/properties in all components
Status: NEW
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Rules / jBPM integration, SwitchYard
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: kconner
QA Contact: Matej Melko
Depends On:
TreeView+ depends on / blocked
Reported: 2014-08-26 15:25 UTC by Tomas Rohovsky
Modified: 2016-01-04 07:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:
Type: Feature Request

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Issue Tracker SWITCHYARD-2288 Major Open Provide propagating of headers/properties in all components 2016-05-10 11:15:18 UTC

Description Tomas Rohovsky 2014-08-26 15:25:37 UTC
Currently, only Camel provides propagation of inbound message headers and exchange properties to the outbound contexts. As Keith said, this is implementation specific. It would be nice to provide that in other components. From what I have tried, it doesn't work for bean, BPM, Drools. I haven't tested that on BPEL yet.

(03:39:31 PM) kcbabo: trohovsk: when it comes to headers, camel has a certain way that it treats headers between invocations
(03:40:11 PM) kcbabo: trohovsk: this mechanism is unique to camel
(03:40:34 PM) kcbabo: trohovsk: but there are other things that are different between implementation types as well
(03:40:40 PM) kcbabo: trohovsk: they are completely different domains
(03:41:05 PM) kcbabo: trohovsk: I understand that if you look at header propagation as a system-wide feature, then it looks odd
(03:41:31 PM) kcbabo: trohovsk: but header propagation is a detail specific to each implementation - each implementation has their own mechanism for how headers are handled
(03:42:07 PM) kcbabo: trohovsk: we could possibly provide an enhancement which allows other implementation types to automatically propagate headers
(03:42:40 PM) kcbabo: trohovsk: possibly by introducing another exchange scope

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