[dna-issues] [JBoss JIRA] Commented: (DNA-457) Add JSR-170 Locking Optional Feature
Brian Carothers (JIRA)
jira-events at lists.jboss.org
Mon Oct 19 15:55:05 EDT 2009
[ https://jira.jboss.org/jira/browse/DNA-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12490418#action_12490418 ]
Brian Carothers commented on DNA-457:
-------------------------------------
Committed patch that provides a locking implementation based on tracking the UUIDs of locked nodes. This implies that any lockable node must also be referenceable. The patch allows all of the TCK locking tests to pass as well as a few L2 tests which assumed a locking implementation for the repository. However, the locking approach does not yet provide any way of integrating the lock/unlock capabilities with the underlying repository. I will leave the defect open until that need can be addressed as well.
Thanks much for the reviews and suggestions!
> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
> Key: DNA-457
> URL: https://jira.jboss.org/jira/browse/DNA-457
> Project: DNA
> Issue Type: Feature Request
> Components: JCR
> Affects Versions: 0.5
> Reporter: Brian Carothers
> Fix For: 1.0
>
> Attachments: DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features. The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the dna-issues
mailing list