We are presently are using the Java broker have now found a need to send message with the destination address in some messages different than the default address for a session.
I was wondering if the Java Broker still has a problem with setting routing key at message level (can not set the message's routing key different than the session was created with) as described in ncdc's answer in: http://stackoverflow.com/questions/9189379/apache-qpid-set-routing-key-at-message-level He points out in: https://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/client/BasicMessageProducer_0_10.java, you'll see code like this: String routingKey = destination.getRoutingKey().toString();if (deliveryProp.getRoutingKey() == null || ! deliveryProp.getRoutingKey().equals(routingKey)){ deliveryProp.setRoutingKey(routingKey);} which would mean that even if you set a routing key on your message, it will be replaced by the destination's routing key if the message's routing key differs from the destination's routing key. I still see this code at this link, but I don't know if this is still the active code. If so, does this apply to "messaging" lib (vs. the "client" lib)? Also, does this apply if using a C++ client into the Java broker? And/or a Java client into the Java broker? If still a limition of the Java broker, is it also a limitation of the C++ broker? thanks, Tom
