For receiving messages, you can try to use address like this when creating
the receiver:
<queueName>; { node: { type: queue } , create: never , mode: consume ,
assert: never }
For sending you can either use the same to publish messages directly to the
queue or if you need to send the message to some specific exchange with
some routing key, you can use this:
<exchange>/<routingKey>; { node: { type: topic }, create: never }
These addresses should not create anything. The only ACL rights they need
are the "access" right to verify that the queue / exchange exist and the
consume/publish right.
Jakub
On Fri, Oct 9, 2015 at 3:27 PM, trivedi_ravi13 <[email protected]>
wrote:
> Is there a control in qpid python messaging APIs if we don't want to create
> or bind the queue ( already done by some one else ) but just want to send
> or
> receive the message ? I am using ACL and some of the applications are not
> allowed to perform any action except send or receive. Like in old client
> APIs we had different APIs for create and bind.
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/Bind-control-in-Python-messaging-APIs-tp7632090.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
