Task #724
Story #957: CN Service layer should be refactored for 0.6 release
Dates in java not storing milliseconds
Status:
Closed
Priority:
High
Assignee:
Robert Waltz
Category:
d1_cn_service
Target version:
Start date:
Due date:
% Done:
100%
Milestone:
CCI-0.5
Product Version:
*
Story Points:
Sprint:
Description
currently for the synchronization to work correctly, need to use the following code to round up to the next second:
when updating the lastHarvestedDate i use the following calculation:
lastMofidiedDate.setTime(lastMofidiedDate.getTime() + (1000 -(lastMofidiedDate.getTime()%1000)));
this will lead to loss of data
History
#1 Updated by Robert Waltz about 14 years ago
- Parent task set to #957
- Milestone set to CCI-0.6
#2 Updated by Robert Waltz about 14 years ago
- Milestone changed from CCI-0.6 to CCI-0.5
#3 Updated by Robert Waltz over 13 years ago
Ben of the benMac moniker may have some insight from the metacat side of things
#4 Updated by Robert Waltz over 13 years ago
- Status changed from New to Closed
- translation missing: en.field_remaining_hours set to 2.0
Confirmed that CN stack is manipulating the milliseconds correctly.
