Bug 820665

Summary: queue route forwarding enhancement
Product: Red Hat Enterprise MRG Reporter: Andrew Replogle <areplogl>
Component: qpid-cppAssignee: messaging-bugs <messaging-bugs>
Status: NEW --- QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 2.1CC: jross
Target Milestone: ---Keywords: Improvement
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 Andrew Replogle 2012-05-10 15:47:09 UTC 
Enhancement request:

Currently source queue's in queue routes dequeue the message after forwarding it on to the exchange destination. 

I can see use-case scenarios where it would be very useful to have an option when creating the route to leave the original copy of the message on the source queue when forwarding it to the destination exchange. 

Scenario:

An organization wants to expand functionality of their application that would require a subset of the messages currently being delivered to the queue in question. Instead of modifying the existing application components that consume and publish to these queues to also deterministically publish the subset of messages to the new queues, allow the queue route to only forward and not move messages to an intelligent exchange.

Then the exchange (XML in this scenario) can route the messages via the bindings if the xquery matches. 

This would allow the organization to expand their application without spending additional hours retro-fitting existing messaging calls for the new components.