activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Mittler (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQCPP-88) Remove setCMSMessageId from CMS API
Date Fri, 16 Mar 2007 12:09:34 GMT

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

Nathan Mittler resolved AMQCPP-88.
----------------------------------

    Resolution: Won't Fix

There were some unit tests that were calling this method.  So rather than removing this method,
I've added better comments to make it more clear the purpose of this method. This work was
done under AMQCPP-89.



> Remove setCMSMessageId from CMS API
> -----------------------------------
>
>                 Key: AMQCPP-88
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-88
>             Project: ActiveMQ C++ Client
>          Issue Type: Task
>          Components: CMS Impl
>    Affects Versions: 1.1, 2.0
>            Reporter: Nathan Mittler
>         Assigned To: Nathan Mittler
>            Priority: Trivial
>             Fix For: 2.0
>
>
> Message ID is a provider defined value and should not be settable from the CMS API. 
Although this deviates from JMS, the NMS client already makes this property read-only.
> The JMS API says the following for the setJMSMessageId method:
> "JMS providers set this field when a message is sent. This method can be used to change
the value for a message that has been received."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message