activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Strasheim (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (AMQCPP-89) Case of cms::Message getter and setter names are not consistent with case of JMS Message getter and setter names
Date Fri, 16 Mar 2007 11:21:34 GMT

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

Albert Strasheim reopened AMQCPP-89:
------------------------------------


Looks like you might have missed getCMSTimeStamp/setCMSTimeStamp. JMS Message spells it "Timestamp".

> Case of cms::Message getter and setter names are not consistent with case of JMS Message
getter and setter names
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-89
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-89
>             Project: ActiveMQ C++ Client
>          Issue Type: Improvement
>          Components: CMS Impl
>    Affects Versions: 2.0
>            Reporter: Albert Strasheim
>         Assigned To: Nathan Mittler
>            Priority: Minor
>             Fix For: 2.0
>
>
> The cms::Message getter and setter names could be more consistent with the JMS Message
getter and setter names. It makes sense that JMS is replaced with CMS, but there are case
inconsistencies that are slightly suboptimal.
>  * getJMSCorrelationID vs getCMSCorrelationId
>  * setJMSCorrelationID vs setCMSCorrelationId
>  * getJMSMessageID vs setCMSMessageId
>  * getJMSTimestamp vs getCMSTimeStamp
> I think it might be worth fixing these for the 2.0 release. It's especially useful when
one quickly wants to port over a bit of JMS code to CMS.

-- 
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