You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/12/06 12:41:11 UTC
[jira] Commented: (JCR-2824) Add RepositoryException to
JackrabbitAccessControlList#getRestrictionNames and #getRestrictionType
[ https://issues.apache.org/jira/browse/JCR-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967158#action_12967158 ]
Jukka Zitting commented on JCR-2824:
------------------------------------
Merged to the 2.2 branch in revision 1042591.
> Add RepositoryException to JackrabbitAccessControlList#getRestrictionNames and #getRestrictionType
> --------------------------------------------------------------------------------------------------
>
> Key: JCR-2824
> URL: https://issues.apache.org/jira/browse/JCR-2824
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-api
> Affects Versions: 2.0.0, 2.0.3, 2.1.0, 2.1.1, 2.1.2
> Reporter: angela
> Assignee: angela
> Fix For: 2.2.0
>
>
> Throughout the JCR and Jackrabbit API methods that include name processing are define to throw RepositoryException in case of
> an error related to name processing (due to lack of a more specific exception in the javax.jcr package space).
> Unfortunately, I forgot those in JackrabbitAccessControlList and JackrabbitAccessControlEntry. While the latter has already been addressed for the 2.2 release,
> I would like to fix the JackrabbitAccessControlList interface as well (and subsequently also fix the implementations that currently do not properly cope with
> names).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.