The new Bridge is very handy when integrating with different providers, but when that works there is a "small" added feature that could give a lot of value to developers: correlating messages on different providers. It would be very interesting to see if a simple and elegant solution such as the Bridge could be explored further to aid this common scenario. Here are some thoughts... The specification clearly states that message id's don't need to be unique across providers, this always cuts down to creating custom solutions for replying to external JMS messages. ReplyTo indicates specifying a Destination, which is not relevant when going across providers. Directly after sending a message the provider's jms message id is available in the message object on the client side. If the Bridge were to make that id available somehow it would be trivial to map id's between providers. Let's say there are two bridge instances set up: 1) Listens to local queue "outbound" and sends to remote provider "in" 2) Listens to remote provider "out" and sends to local queue "inbound" If the message id obtained from sending at "1" were available somehow, we could either allow "2" to map the message (most powerful) or add a property of kind, allowing other code (perhaps the listener on "inbound") to understand the mapping. Any thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051708#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...