[
https://issues.apache.org/jira/browse/OAK-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803168#comment-13803168
]
Tobias Bocanegra edited comment on OAK-1111 at 10/23/13 7:14 PM:
-----------------------------------------------------------------
can we just use
{{org.apache.jackrabbit.core.persistence.util.BundleWriter#writeDate()}} as
it's a compact and fast way of storing the calendar. and it's proven to work
for a long time now.
Also note, that the JCR API deliberately uses Calendar (over a simple
timestamp) in order to preserve the timezone information.
was (Author: tripod):
can we just use
{{org.apache.jackrabbit.core.persistence.util.BundleWriter#writeDate()}} as
it's a compact and fast way of storing the calendar. and it's proven to work
for a long time now.
> 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
> 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)
