In my experience I have seen the AMQP request/reply implemented always with the messageid (set at requestor) copied into the reply correlationid (set at responder); it's also the default way in the "great" EIP book :-)
We know that JMS doesn't provide the way to set the messageid (but only the correlationid). Do you think that is so important for an application specifying the messageid and don't use the automatically generated by the library (as JMS client works) ?
Tha main point is that JMS should allow to retrieve the messageid for a message sent so that the application can handle the correlation on reply.
Of course the AMQP specification doesn't impose anything on the way to use.
Paolo.
Paolo PatiernoSenior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
From: dejanb@xxxxxxxxxxxx
Date: Fri, 24 Jun 2016 13:43:47 +0200
To: hono-dev@xxxxxxxxxxx
Subject: Re: [hono-dev] Correlation of messages
Hi Kai,
I’m +1 for using correlation id pattern here. It doesn’t impact anything fundamentally (it’s not jms related), and leaves option for implementations that want to use message ids, to set them as correlation ids if they want to.
_______________________________________________
hono-dev mailing list
hono-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/hono-dev