[
https://issues.apache.org/jira/browse/JCR-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676621#action_12676621
]
Martijn Hendriks commented on JCR-1996:
---------------------------------------
Marcel, thanks for your quick response and patch! I noticed that retrieving the
value through the JCR API will not work for the big dates (even when the
repository is restarted):
Caused by: javax.jcr.ValueFormatException: empty value
at org.apache.jackrabbit.value.DateValue.getDate(DateValue.java:139)
Is this also solved by the patch?
> Handle date values in the far future or prevent these from being persisted
> --------------------------------------------------------------------------
>
> Key: JCR-1996
> URL: https://issues.apache.org/jira/browse/JCR-1996
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: indexing, jackrabbit-core
> Affects Versions: 1.5.3
> Reporter: Martijn Hendriks
> Attachments: JCR-1996.patch
>
>
> Setting a date property with a value in the far future (e.g., the year 20009)
> and saving the session causes the index component to throw an exception (see
> the DateField#timeToString method). Furthermore, when the repository is
> restarted, the properties' value cannot be retrieved anymore because of a
> ValueFormatException caused by an empty value. Restarting the repository with
> an empty search index does not work because indexing fails. I haven't looked
> into the effect on queries.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
