[
https://issues.apache.org/jira/browse/SLING-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758766#action_12758766
]
Felix Meschberger commented on SLING-1122:
------------------------------------------
Actually, the jcr:lastModified property is generally of type date so conversion
to long is a no-brainer (and defined by the JCR spec). The problem comes in if
an application writes the property as a String which is not readily convertible
into a long value (we could of course try to round-trip through Calendar, which
should work IIRC).
For the log level: I would log at warn (it is probably an issue, that the
jcr:lastModified cannot be converted to long because this indicates a bug or
misuse somewhere) or a debug. Informational sounds not quite correct to me here.
> JcrNodeResource should better ignore jcr:lastModified if that's not a long
> --------------------------------------------------------------------------
>
> Key: SLING-1122
> URL: https://issues.apache.org/jira/browse/SLING-1122
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.0.4
> Reporter: Bertrand Delacretaz
> Fix For: JCR Resource 2.0.6
>
>
> The message logged by JcrNodeResource if a node's jcr:lastModified property
> cannot be converted to a long is not very informative, should be improved.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
