Bug 779867 (SOA-2226)
| Summary: | ReplyTo EPR must be manually reset after Aggregator action is used | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Kevin Conner <kevin.conner> |
| Component: | JBossESB | Assignee: | Kevin Conner <kevin.conner> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.2 | CC: | kevin.conner, sadurudeen.kuthbudeen.z01 |
| Target Milestone: | --- | ||
| Target Release: | 5.1.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2226 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-17 10:36:35 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
Kevin Conner
2010-08-11 13:48:43 UTC
Link: Added: This issue depends JBESB-3311 Link: Added: This issue is incorporated by SOA-2210 Writer: Added: Darrin Release Notes Docs Status: Added: Not Yet Documented 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. 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. 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. 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. |