We have tried a number of things.
The first was to embed what we thought were AMQP 1.0 options on the command
line from the grokbase post mentioned above like so:
simple_recv -a '127.0.0.1:5673/abc; { create:always,
connection:{name:'con1'},link:{name:'link1'},node:{type:queue,x-declare:{auto-delete:false,durable:true}}}'
This does not appear to do anything and I cannot find property definitions
for "link" or "node" anywhere, so I assume they do not exist, though for
whatever reason seemed to work for that guy.
We are also using the QpidJMS library for the WebSocket support, so we are
currently just using Session.createConsumer(), to get ourselves off of the
ground, and then we will look at more of the APIs such as
Session.createDurableConsumer(), and more. Unfortunately, the JMS
implementation appears to hide some details of proton-j, so I'm trying to
understand the connection between the two. It seems like some of the
options are watered down to fit JMS, but I hope it will still do what we
need.
We are taking a closer look at the c++ example Justin pointed us to above.
It looks like that has access to options that are actually specified in the
AMQP 1.0 spec for the given objects like Session, Source, Target, etc.
We still need to figure out if our dispatch router, C++ broker pair can play
nicely together to allow the objects to be created on the broker.
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
