[
https://issues.apache.org/jira/browse/SLING-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180389#comment-14180389
]
Stefan Seifert commented on SLING-4088:
---------------------------------------
looks ok for me - all my usecases pass with this implementation as well.
(although i'm a bit puzzled with storing the data object as serialized binary
in the JCR when writing a data via MVP - but if this is really existing
behavior to be kept. the date object stored this way is not directly usable via
JCR API. when only using the ValueMap this subtle difference is never noticed,
but if the property is accessed in any other way you get only data garbage)
> Regression introduced by SLING-3846 : JcrModifiableValueMap: Date object not
> supported for writing data
> -------------------------------------------------------------------------------------------------------
>
> Key: SLING-4088
> URL: https://issues.apache.org/jira/browse/SLING-4088
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.3.8, JCR Resource 2.3.10
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.3.12
>
>
> With the patch of SLING-3846, putting a Date object into a resource, reading
> the resource back and trying to get a Date object, results in a
> ClassCastException as now a Calendar object is returned.,
> This breaks existing code and I think we should revert SLING-3846
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
