[
https://issues.apache.org/jira/browse/OAK-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804369#comment-13804369
]
Jukka Zitting commented on OAK-1111:
------------------------------------
Fixed in http://svn.apache.org/r1535431 by using ISO 8601 -formatted strings
for storing date values. Currently the string gets parsed every time (i.e. no
memoization) a date value is accessed as a Calendar, long, double or
BigDecimal. That doesn't seem to impact our existing benchmarks.
> Node#setProperty(String, Calendar) doesn't take time zone in account
> --------------------------------------------------------------------
>
> Key: OAK-1111
> URL: https://issues.apache.org/jira/browse/OAK-1111
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, jcr
> Reporter: Antonio Sanso
> Priority: Critical
> Fix For: 0.11
>
> Attachments: OAK-1111-test.txt
>
>
> Node#setProperty(String, Calendar) doesn't take time zone in account.
> It looks the Calendar value is straightly stored as a long without take in
> consideration the time zone,
> Unit test to follow
--
This message was sent by Atlassian JIRA
(v6.1#6144)
