[
https://issues.apache.org/jira/browse/JCR-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg resolved JCR-2281.
------------------------------------
Resolution: Won't Fix
on second thought i'm not sure whether there's a legitimate use-case for this
'feature'.
resolving as 'won't fix' for now.
> auto-compute jcr:lastModified value on server
> ---------------------------------------------
>
> Key: JCR-2281
> URL: https://issues.apache.org/jira/browse/JCR-2281
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-core
> Reporter: Stefan Guggisberg
> Fix For: 2.0.0
>
>
> in a client-server setup setting the jcr:lastModified property on the client
> can cause problems due to unsynchronized client & server time.
> ideally a remote jcr client should be able to indicate that the server should
> automatically set the jcr:lastModified value when persisting the changes,
> e.g. by setting it to 0 (utc 1970-1-1).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
