jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Sapunov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-67) Node.canAddMixin(String)
Date Sun, 12 Nov 2006 23:13:48 GMT
    [ http://issues.apache.org/jira/browse/JCR-67?page=comments#action_12449190 ] 
Dmitry Sapunov commented on JCR-67:


I have comment for the following issue: 

The comment starts here:

"after the spec this method must return false if the node is locked."

This is not exactly true, by specification JSR170 at least: 

1. In those repositories that support it, locking allows a user to
temporarily lock nodes in order to prevent OTHER users from changing
them (8.4) 
2. "A lock would prevent the addition of the mixin" () - definetely
is not the same as "node is locked". Just because of (1) - lock may
prevent and may allow. (7.4.3) 
3. Effect of a lock - node cannot be changed by anyone except the
user who is the token holder for that lock.(8.4.8) 
and 4. More precisely, a lock applying to a node prevents all
non-token holders from doing any of the following: Adding or removing
its mixin node types. (same 8.4.8) 

So, IMO, the Node.canAddMixin() must return false for non-tocken
holders, and work as usual for tocken holders. 

wbr, dMitry

> Node.canAddMixin(String)
> ------------------------
>                 Key: JCR-67
>                 URL: http://issues.apache.org/jira/browse/JCR-67
>             Project: Jackrabbit
>          Issue Type: Bug
>            Reporter: Vinzenz Wyser
>         Assigned To: Stefan Guggisberg
> after the spec this method must return false if the node is locked.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message