The client's responsibility is to say "I want to send to this destination
<foo> and I assert that <foo> is a queue". This is what the client does.
It is up to the server side to validate the assertion that the client is
making. The client has no information as to whether the server is lying or
not. The error you encountered was purely because of the bug on the server
(Azure) side (it was saying "your assertion is correct, <foo> is a queue"),
there is nothing more that the client can do.
-- Rob
On Tue, 31 Jul 2018 at 16:46, akabhishek1 <mailbox.abhishek.ku...@gmail.com>
wrote:
> Hi Tim,
>
> I have created
>
> Destination dest = session.createQueue("test-resource");
>
> I am expecting message should go in Queue and if "queue" is not available
> then throw
> exception.
>
> Current Behaviour - If "test-resource" named topic exists instead of a
> Queue
> then message is successfully delivered to topic "test-resource" instead of
> throwing exception.
>
> Feature Request - if i create Queue Destination then message should go in
> Queue and if same resource not available as Queue then throw exception.
>
> Please let me know for any concern/question.
>
> Regards,
> Abhishek Kumar
>
>
>
>
> --
> Sent from:
> http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
