[
https://issues.apache.org/jira/browse/JCR-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481681
]
Julian Reschke commented on JCR-779:
------------------------------------
Actually, it probably will not be sufficient. The store I'm currently working
with requires the timeout to be known at the time of lock creation (and the
other one I'm familiar with does so as well). As lock creation writes directly
to the workspace, it seems that we really need a lock() method with additional
parameters, after all.
> Timeout for Session and/or Lock
> -------------------------------
>
> Key: JCR-779
> URL: https://issues.apache.org/jira/browse/JCR-779
> Project: Jackrabbit
> Issue Type: New Feature
> Components: locks
> Environment: All environments
> Reporter: Sridhar
> Priority: Minor
>
> I think there needs to be a mechanism where we can set the timeout for a
> particular jcr Session. Or at the most, there should be a provision to set a
> timeout for a lock on a node.
> Hope this is implemented soon.
> Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
