[ https://issues.apache.org/jira/browse/QPID-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu resolved QPID-4566. ------------------------------------ Resolution: Won't Fix Currently there are no compelling reasons to implement this. This use case was incorrectly given as a reason for allowing the message-id to contain a non UUID string. Please see QPID-4566 for the correct use case. > 0-10 JMS Message Delegate should allow a non UUID String to be set as > message-id > --------------------------------------------------------------------------------- > > Key: QPID-4566 > URL: https://issues.apache.org/jira/browse/QPID-4566 > Project: Qpid > Issue Type: Bug > Components: Java Client > Affects Versions: 0.20 > Reporter: Rajith Attapattu > Assignee: Rajith Attapattu > Priority: Minor > Labels: JMS, JMS-Compliance > Fix For: 0.21 > > > The0-10 JMS Message Delegate does not allow a non UUID to be set as > message-id. This is due to the underlying AMQP 0-10 version requiring the > message-id to be a UUID. > However this causes issues when a Qpid message is sent through a 3rd party > MessageProducer. Ex in a Message Bridge. > The Message delegate should allow any String to be set (as long as it's > prefixed with "ID:" as the Message ID. > This does not affect the Qpid 0-10 based JMS Message Producer as the send > implementation will set a UUID as the message-id. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org