qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajith Attapattu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-4566) 0-10 JMS Message Delegate should allow a non UUID String to be set as message-id
Date Mon, 04 Feb 2013 20:52:13 GMT

     [ https://issues.apache.org/jira/browse/QPID-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajith Attapattu updated QPID-4566:
-----------------------------------

    Labels: JMS JMS-Compliance  (was: )
    
> 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
>            Reporter: Rajith Attapattu
>            Priority: Minor
>              Labels: JMS, JMS-Compliance
>
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message