[
https://issues.apache.org/jira/browse/JCR-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCR-3195.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.5
> wrong assumptions in test cases about lock tokens
> -------------------------------------------------
>
> Key: JCR-3195
> URL: https://issues.apache.org/jira/browse/JCR-3195
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-tests, test
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Fix For: 2.5
>
>
> Several test cases assume that Lock.getLockToken has to return null for locks
> not attached to the current session. However, this is optional. Citing the
> Javadoc for getLockToken:
> * May return the lock token for this lock. If this lock is open-scoped
> and
> * the current session either holds the lock token for this lock, or the
> * repository chooses to expose the lock token to the current session,
> then
> * this method will return that lock token. Otherwise this method will
> * return <code>null</code>.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
