In terms of sending maps/lists I think we said (at OASIS), though it is possibly not yet in the draft spec, that Json formatted equivalents should be able to be used for all values... however I have no idea if the Dispatch Router supports that.
In terms of receiving lists / maps I would assume that treating the received JMS Message as an ObjectMessage and casting that result to the correct type (List or Map as appropriate) will always work? Though I should probably wait for Robbie to step in on this one :-) -- Rob On 18 January 2017 at 11:39, Gordon Sim <[email protected]> wrote: > 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-vcvRAhVn0YMKHTvABMEQFg > gfMAA&url=https%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2F > download.php%2F52425%2Famqp-man-v1%25200-wd08.pdf&usg=AFQjCN > EDHTcSb8gSA2Uqx-bAkupHHcn92A > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
