[
https://issues.apache.org/jira/browse/SLING-9090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-9090.
----------------------------------------
Resolution: Fixed
Thank you [~angela] for your patch and sorry that it took us so long to get to
it.
I have applied it in [commit
bd3e865|https://github.com/apache/sling-org-apache-sling-jcr-repoinit/commit/bd3e865442ffbf02722a5f36020ca75dab4906f6],
with minor changes to use more specific exception checking instead of
@Test(expected... where that makes sense and taking into account some other
changes that happened in the meantime. Please cross-check!
> AclLine.Action.REMOVE and AclLine.Action.REMOVE_ALL not handled in jcr
> implementation
> -------------------------------------------------------------------------------------
>
> Key: SLING-9090
> URL: https://issues.apache.org/jira/browse/SLING-9090
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Affects Versions: Repoinit JCR 1.1.6, Repoinit JCR 1.1.8, Repoinit JCR
> 1.1.10, Repoinit JCR 1.1.12, Repoinit JCR 1.1.14, Repoinit JCR 1.1.16,
> Repoinit JCR 1.1.18, Repoinit JCR 1.1.20, Repoinit JCR 1.1.22, Repoinit JCR
> 1.1.24, Repoinit JCR 1.1.26
> Reporter: Angela Schreiber
> Assignee: Bertrand Delacretaz
> Priority: Major
> Fix For: Repoinit JCR 1.1.32
>
>
> [~bdelacretaz], while the documentation and the parser code provides the
> ability to remove an individual or all access control entries, it seems the
> JCR implementation doesn't actually support it.
> using it may lead to odd side effects or failures.... so, i think either the
> parser should remove the support for Action.REMOVE and Action.REMOVE_ALL or
> the jcr implementation part should respect it... at the very minimum it
> should spot any usage of it and fail the repo-init if there is no way to
> implement it properly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
