activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQNET-85) ActiveMQMessage.Expiration should autoconvert the ticks to .NET from Java and vice versa just as NMSTimestamp does
Date Thu, 29 May 2008 04:04:00 GMT

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

Jim Gomes resolved AMQNET-85.
-----------------------------

    Resolution: Won't Fix

The Expiration and Timestamp properties of the Message base class are correctly stored in
Java time format.  These time values are marshaled on the wire to/from ActiveMQ.  The correct
method for accessing these values is through the NMSTimestamp and NMSTimeToLive accessor properties.
 If the low-level properties were changed, then timestamps would break.

Further, it is highly recommended to program to the NMS API using the abstract NMS API layer
rather than at the lower level ActiveMQ client implementation level.

> ActiveMQMessage.Expiration should autoconvert the ticks to .NET from Java and vice versa
just as NMSTimestamp does
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQNET-85
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-85
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: ActiveMQ Client
>            Reporter: Brandon Bethke
>            Assignee: Jim Gomes
>            Priority: Minor
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> The NMSTimstamp property will convert the java ticks in .NET ticks and vice versa. ActiveMQMessage.Expiration
should do the same.

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