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 2010/08/20 11:41:17 UTC
[jira] Commented: (JCR-2620) Authorizable#getProperty and
#setProperty should deal with relativePath
[ https://issues.apache.org/jira/browse/JCR-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900656#action_12900656 ]
angela commented on JCR-2620:
-----------------------------
Work in progress commit at revision 987435 making the following changes:
- Authorizable#getPropertyNames(String relPath) NEW
- Authorizable#hasProperty, #getPropery, #setProperty and #removeProperty not only deal with names but also with relative paths.
- UserManager#findAuthorizable changed to deal both with a property name and a relative path.
TODO:
- add more tests for Authorizable property handling
- add tests for UserManager#findAuthorizable with relative paths
> Authorizable#getProperty and #setProperty should deal with relativePath
> ------------------------------------------------------------------------
>
> Key: JCR-2620
> URL: https://issues.apache.org/jira/browse/JCR-2620
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-api, jackrabbit-core
> Affects Versions: 2.0.0, 2.1.0
> Reporter: angela
> Assignee: angela
> Fix For: 2.2.0
>
>
> Authorizable#getProperty and #setProperty defines the property to be identified by a name.
> The JCR item based implementation could easily deal with relative paths instead and also retrieve or write properties below child
> nodes of the rep:Authorizable node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.