Hide Forgot
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=864653&gid=1354 project_key: SOA Include fix for JBESB-3308 The ESB depends on the message's replyTo to know where to send a reply in a RequestResponse service. However, the Aggregator action makes no attempt to preserve the replyTo when it creates an aggregate message for a series. In most cases, I would think the replyTo on the aggregated messages would be the same, so adding it onto the resulting aggregated message would seem like a good idea. Otherwise, it has to be handled manually in the assembler action.
Link: Added: This issue incorporates JBESB-3308
This has already been addressed, should be present in ER1
Temporarily reopening to update release note info.
Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3308 The ESB depends on the message's replyTo to know where it has to send a RequestResponse service reply. However, the Aggregator action made no attempt to preserve the replyTo when it created an aggregate message for a series. To resolve this issue, it now only maps an end-point reference onto the aggregated message if all of the messages attached to the aggregated message have the same EPR. In most cases, I would think the replyTo on the aggregated messages would be the same, so adding it onto the resulting aggregated message would seem like a good idea. Otherwise, it has to be handled manually in the assembler action.