Bug 779867 (SOA-2226) - ReplyTo EPR must be manually reset after Aggregator action is used
Summary: ReplyTo EPR must be manually reset after Aggregator action is used
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2226
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.0.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0 GA
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-11 13:48 UTC by Kevin Conner
Modified: 2011-02-17 10:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-17 10:36:35 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2226 0 None None None Never

Description Kevin Conner 2010-08-11 13:48:43 UTC 
project_key: SOA
Comment 1 Kevin Conner 2010-08-11 13:49:01 UTC 
Link: Added: This issue depends JBESB-3311
Comment 2 Kevin Conner 2010-08-11 13:49:58 UTC 
Link: Added: This issue is incorporated by SOA-2210
Comment 3 Laura Bailey 2010-12-17 00:41:28 UTC 
Writer: Added: Darrin
Comment 4 Laura Bailey 2010-12-17 00:47:58 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Comment 6 Kevin Conner 2011-02-17 10:20:20 UTC 
Any ReplyTo EPR which was present on the incoming messages to the Aggregator was never being propagated to the aggregated message.  As a result it was necessary to explicitly set the EPR using a pipeline action after the aggregator.

The incoming EPR is now propagated to the aggregated message provided that all incoming messages specify the same EPR.
Comment 7 Dana Mison 2011-02-17 10:30:01 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: Any ReplyTo EPR which was present on incoming messages to the Aggregator was not being propagated to the aggregated message.  As a result it was necessary to explicitly set the EPR using a pipeline action after the aggregator.  Now, if the same EPR is present on each of the incoming messages to the aggregator then that EPR will be propagated to the aggregated message.
Comment 8 Dana Mison 2011-02-17 10:32:02 UTC 
Release Notes Text: Removed: Any ReplyTo EPR which was present on incoming messages to the Aggregator was not being propagated to the aggregated message.  As a result it was necessary to explicitly set the EPR using a pipeline action after the aggregator.  Now, if the same EPR is present on each of the incoming messages to the aggregator then that EPR will be propagated to the aggregated message. Added: Any ReplyTo EPR which was present on incoming messages to the Aggregator were  not being propagated to the aggregated message.  As a result it was necessary to explicitly set the EPR using a pipeline action after the aggregator.  Now, if the same EPR is present on each of the incoming messages to the aggregator then that EPR will be propagated to the aggregated message.
Comment 9 Dana Mison 2011-02-17 10:36:35 UTC 
Release Notes Text: Removed: Any ReplyTo EPR which was present on incoming messages to the Aggregator were  not being propagated to the aggregated message.  As a result it was necessary to explicitly set the EPR using a pipeline action after the aggregator.  Now, if the same EPR is present on each of the incoming messages to the aggregator then that EPR will be propagated to the aggregated message. Added: Any ReplyTo EPR which was present on incoming messages to the Aggregator was  not being propagated to the aggregated message.  As a result it was necessary to explicitly set the EPR using a pipeline action after the aggregator.  Now, if the same EPR is present on each of the incoming messages to the aggregator then that EPR will be propagated to the aggregated message.
Note You need to log in before you can comment on or make changes to this bug.