Red Hat Bugzilla – Bug 626859
New Address treated different in C++ and Java
Last modified: 2013-02-25 06:06:39 EST
Description of problem:
RMG 1.3 beta handles new address different between C++ and Java client API
Version-Release number of selected component (if applicable):
RMG 1.3 beta
The following address work with C++ but not Java
The following address work with Java but not Java
Steps to Reproduce:
The java client should use a nested arguments map rather than trying to interpret arguments itself. This will align it with the python and c++ clients as well as ensuring that arbitrary arguments can be passed through as needed.
There are two issues from the java client side.
1. It just ignores arguments option specified under x-declare.
2. The JMS client does not use the main exchange as the default in case
an exchange is not included in the x-bindings.
(In reply to comment #2)
> There are two issues from the java client side.
> 1. It just ignores arguments option specified under x-declare.
This is tracked via QPID-2845
> 2. The JMS client does not use the main exchange as the default in case
> an exchange is not included in the x-bindings.
This is tracked via QPID-2844
The following commits were applied to the internal release branch.