[
https://issues.apache.org/jira/browse/QPID-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217924#comment-15217924
]
Keith Wall commented on QPID-7158:
----------------------------------
We will change the model attributes that have type long but are in actual fact
Dates into java.util.Dates so that the model properly advertises its type.
This will involve changes to CO#createdTime/lastUpdatedTime attributes on ACO,
Queue#oldestMessageAge, Connection#lastIoTime, Session#transactionStartTime
etc, BDBHARemoteReplicationNode#joinTime. There may be others.
We want the JSON representing objects with timestamps to remain unchanged. To
achieve this, for the inbound we need an AttributeValueConverter that converts
from a Longs (or Strings containing Longs) into Dates. For the outbound, we
will need to use Jackson's WRITE_DATES_AS_TIMESTAMPS serialisation feature
(default, I think).
> [Java Broker] Change type of datetime management attributes from Long to
> java.util.Date
> ---------------------------------------------------------------------------------------
>
> Key: QPID-7158
> URL: https://issues.apache.org/jira/browse/QPID-7158
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Alex Rudyy
> Fix For: qpid-java-6.1
>
>
> It is unclear from metadata that datetime attribute having type Long
> actually represent datetime values. We need to change datetime attributes
> type from Long to java.util.Date which can still be serialized into json as
> long values
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
