[
https://issues.apache.org/jira/browse/JCR-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2990:
------------------------
Priority: Minor (was: Major)
as far as I saw there this doesn't have an impact to the overall functionality
but having the
warnings in the logs is ugly anyway.
> Jcr-Server: Token exposed for Session-Scoped Locks results in "Bad lock
> token" Exception when being reapplied.
> --------------------------------------------------------------------------------------------------------------
>
> Key: JCR-2990
> URL: https://issues.apache.org/jira/browse/JCR-2990
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server
> Reporter: angela
> Assignee: angela
> Priority: Minor
>
> this is a consequent of JCR 2.0 lock token handling that doesn't expose the
> session-scoped lock tokens any more.
> while having a workaround in JcrActiveLock is fine to expose some sort of
> lock token to the DAV client the
> corresponding code used to re-apply the lock tokens to an existing session
> has not been adjusted to cope
> with the fact that session-scoped lock tokens just expose a fake token.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
