Hi All,
Currently we cannot specify arguments for Queue binding and declare, using
the binding URL in the JNDI props file.
This prohibits the JMS client to leverage some of the options offered by the
C++ broker.
a) Use the XML exchange as you need to specify the xpath expression as a
binding argument.
b) Use queue configuration options ( Ex qpid.max_size, qpid.max_count,
qpid.policy_type ...etc)
Another limitation is that a queue could only be bound to a single exchange
(all though now you could specify multiple binding keys).
It would be nice if we found a way to express the above using our JNDI prop
file.
One idea is to use the following format.
bind.args.<prop_name>=<prop_value> and dec.args.<prop_name>=<prop_value> in
the binding URL.
This however doesn't solve the problem of binding to multiple exchanges.
Another idea floated by Martin was to separate the queue definition from its
bindings.
The obvious advantage of this approach is that you could bind your queue to
multiple exchange/bindingkey pairs.
Ex. destination.<jndiname>=myQueue?durable=true&args.qpid.max_size=100000
binding.<jndiname>=myExchange/myQueue?bindingkey='abc'&args.prop1=prop1value&args.prop2=prop2value
binding.<jndiname>=amq.direct/myQueue?bindingKey='xyz'
I am sure there are other ideas as well.
Please help by sharing your ideas on a new propsal or how to refine the
existing mechanism.
(Eitherway we need to ensure backwards compatibility.)
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
