You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2009/09/24 15:14:16 UTC

[jira] Commented: (JCR-2313) Improvements to user management (2)

    [ https://issues.apache.org/jira/browse/JCR-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759113#action_12759113 ] 

angela commented on JCR-2313:
-----------------------------

List of changes 
------------------------------------------------------------------------------------------------------------------------------------ 

- calculate jcr:uuid of user/group nodes from the ID instead of having it generated randomly 
   -> simplify getAuthorizable(String id) to a Session.getNodeByNodeId 
   -> structure of user/group nodes must no longer be defined by the impl 
   -> no need to ignore intermediatePath parameter 
   -> this also remove some limitations of the built-in, config driven node structure 

- make userPath and groupPath configurable. 
  see UserManagerImpl#PARAM_USERS_PATH and UserManagerImpl#PARAM_GROUPS_PATH. 
  If the config option is missing the originally hardcoded values are used as default (-> UserConstants) 

- Referees: remove concept form API and node type definition. 
  After all nobody i asked had strong arguments for the referees and i found myself struggling with the 
  concept that has been part of the initial patch created by christian. 

- rep:userId is redundant now that jcr:uuid is used to lookup a user by id. a human readable form of the id was/is 
  present in the node's name.

> Improvements to user management (2)
> -----------------------------------
>
>                 Key: JCR-2313
>                 URL: https://issues.apache.org/jira/browse/JCR-2313
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-api, jackrabbit-core
>    Affects Versions: 2.0-alpha7, 2.0-alpha8, 2.0-alpha9
>            Reporter: angela
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> follow up issue as JCR-2199 is already closed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.