[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (AMQPBINDMAP-15) Proper handling of correlation ID
[ https://issues.oasis-open.org/browse/AMQPBINDMAP-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell updated AMQPBINDMAP-15: -------------------------------------- Priority: Blocker (was: Major) > Proper handling of correlation ID > --------------------------------- > > Key: AMQPBINDMAP-15 > URL: https://issues.oasis-open.org/browse/AMQPBINDMAP-15 > Project: OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC > Issue Type: Bug > Components: JMS Mapping > Affects Versions: wd06 > Reporter: Steve Huston > Assignee: Robert Gemmell > Priority: Blocker > > Discussed during 22-Sep-2015 TC call. If a JMS application sets correlation ID, a non JMS receiving client reads it and sets as message ID then replies, original client won't understand the received message. > This JIRA should be used to discuss the options for handling the message id and correlation id. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]