On 17/01/17 16:03, Rabih M wrote:
Hello,
If I understood well, Qpid-Dispatch can be managed using Amqp messages.
I saw that the management code is based on proton python binding.
Do you think it is feasible to manage the dispatch router the same way from
Qpid-Jms api?
Yes, but only through an undocumented mechanism that is subject to
change at present. The issue is that it requires sending/receiving AMQP
encoded lists and maps which is not properly supported yet via the JMS API.
Was there any work done in this direction before? Will it be too
complicated to do it?
The protocol is based on the draft of a 'management spec' from OASIS[1].
In general it is very easy to use as long as you can handle AMQP encoded
list and map content.
The router has its own specific entities which are described (though
from the config file perspective) here:
http://qpid.apache.org/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html
The qdmanage tool is very useful for exploring things (e.g. GET-SCHEMA etc).
[1]
https://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjnzIC-vcvRAhVn0YMKHTvABMEQFggfMAA&url=https%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2Fdownload.php%2F52425%2Famqp-man-v1%25200-wd08.pdf&usg=AFQjCNEDHTcSb8gSA2Uqx-bAkupHHcn92A
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
