Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC

  • 1.  JMS messsage-id + correlation-id handling

    Posted 07-19-2016 12:14
    Hi folks, I've been wanting to discuss this at the last couple of aborted meetings, so swapping to mail to perhaps get the ball rolling... In one of the last meetings with significant discussion around JMS, we discussed an issue raised previously with the handling of correlation-id between JMS and non-JMS clients. Some suggested we take discussion to JIRA so I updated https://issues.oasis-open.org/browse/AMQPBINDMAP-15 accordingly, but have had no other comments since. As per a recent comment the issue came up again in a related but different form recently (due to a bug) so I spent some more time thinking about the issue and updated the JIRA again based on that. I've since implemented changes around those thoughts. It would be good to get some feedback on the idea if anyone has some. Robbie


  • 2.  Re: [amqp-bindmap] JMS messsage-id + correlation-id handling

    Posted 07-20-2016 00:14
    Thanks for all your hard work on this Robbie. Btw, I just added a comment to your JIRA ticket that hopefully helps with the thought exercise to validate your approach. cheers, -john. On Tue, Jul 19, 2016 at 5:13 AM Robbie Gemmell < rgemmell@redhat.com > wrote: Hi folks, I've been wanting to discuss this at the last couple of aborted meetings, so swapping to mail to perhaps get the ball rolling... In one of the last meetings with significant discussion around JMS, we discussed an issue raised previously with the handling of correlation-id between JMS and non-JMS clients. Some suggested we take discussion to JIRA so I updated https://issues.oasis-open.org/browse/AMQPBINDMAP-15 accordingly, but have had no other comments since. As per a recent comment the issue came up again in a related but different form recently (due to a bug) so I spent some more time thinking about the issue and updated the JIRA again based on that. I've since implemented changes around those thoughts. It would be good to get some feedback on the idea if anyone has some. Robbie --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- John Fallows CTO    


  • 3.  Re: [amqp-bindmap] JMS messsage-id + correlation-id handling

    Posted 07-20-2016 12:06
    Hi Robbie, I read through the proposal in the JIRA and it looks good to me. The examples you added yesterday are very helpful for understanding how it should work. Thanks. Regards Jakub Scholz ---------------------------------------------------------------------------- Deutsche Börse Services s.r.o. Managing Directors/Geschäftsführung: Michael Gassmann, Mats Andersson. Limited liability company with registered office at Sokolovská 662/136B, CZ-186 00 Prague 8 recorded in the Commercial Register IC: 275 77 015. Maintained by the city court in Prague, Sec. C, File No. 116874. From: Robbie Gemmell <rgemmell@redhat.com> To: amqp-bindmap@lists.oasis-open.org, Date: 19/07/2016 14:13 Subject: [amqp-bindmap] JMS messsage-id + correlation-id handling Sent by: <amqp-bindmap@lists.oasis-open.org> Hi folks, I've been wanting to discuss this at the last couple of aborted meetings, so swapping to mail to perhaps get the ball rolling... In one of the last meetings with significant discussion around JMS, we discussed an issue raised previously with the handling of correlation-id between JMS and non-JMS clients. Some suggested we take discussion to JIRA so I updated https://issues.oasis-open.org/browse/AMQPBINDMAP-15 accordingly, but have had no other comments since. As per a recent comment the issue came up again in a related but different form recently (due to a bug) so I spent some more time thinking about the issue and updated the JIRA again based on that. I've since implemented changes around those thoughts. It would be good to get some feedback on the idea if anyone has some. Robbie --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php ----------------------------------------- Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet. The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited. Legally required information for business correspondence/ Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz: http://deutsche-boerse.com/letterhead


  • 4.  Re: [amqp-bindmap] JMS messsage-id + correlation-id handling

    Posted 07-21-2016 00:49
    Thank you for getting this going, Robbie! And thanks to John for engaging and helping to sort things out. The conference call facility is back in service, so we should be good to go for the call next week. -Steve > On Jul 19, 2016, at 8:13 AM, Robbie Gemmell <rgemmell@redhat.com> wrote: > > Hi folks, > > I've been wanting to discuss this at the last couple of aborted meetings, so swapping to mail to perhaps get the ball rolling... > > In one of the last meetings with significant discussion around JMS, we discussed an issue raised previously with the handling of correlation-id between JMS and non-JMS clients. Some suggested we take discussion to JIRA so I updated https://issues.oasis-open.org/browse/AMQPBINDMAP-15 accordingly, but have had no other comments since. > > As per a recent comment the issue came up again in a related but different form recently (due to a bug) so I spent some more time thinking about the issue and updated the JIRA again based on that. I've since implemented changes around those thoughts. It would be good to get some feedback on the idea if anyone has some. > > Robbie > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >