[
https://issues.apache.org/jira/browse/OAK-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-7233.
-------------------------
Resolution: Fixed
Fix Version/s: 1.9.10
Committed revision 1845334 with the following adjustment to the documentation:
- explicitly mention path-concatenation and the effect on either type of items
- highlight special handling of root path as a consequence of the concat
- link to oak code (but not the jackrabbit code as suggested because this is
the oak documentation)
based on the existing tests i don't think that the examples with paths (but
without wildcard) are wrong. i slightly refactored the documentation in
alignment to the javadoc of {{GlobPattern}}.
finally added some tests to the corresponding exercise in _oak-exercise_
[~stillalex] fyi.
> Improve rep:glob documentation
> ------------------------------
>
> Key: OAK-7233
> URL: https://issues.apache.org/jira/browse/OAK-7233
> Project: Jackrabbit Oak
> Issue Type: Documentation
> Components: core, security
> Reporter: Konrad Windszus
> Assignee: angela
> Priority: Minor
> Fix For: 1.10, 1.9.10
>
>
> The examples at
> https://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html#Examples
> do not explicitly mention the root node. For the root node you must never
> use a {{rep:glob}} starting with {{/}}.
> Also the following points should be clarified:
> * rep:glob affects both (child)node as well as property access
> * a link towards
> https://jackrabbit.apache.org/api/2.8/org/apache/jackrabbit/core/security/authorization/GlobPattern.html
> would be helpful
> * make clearer how a rep:glob ending with {{/}} is different from one not
> ending with {{/}}
> Also the description for
> {{/cat/}} and {{cat/}} seem wrong because IMHO descendants are only
> considered if the glob uses a {{*}}.
> This was originally triggered via
> https://issues.apache.org/jira/browse/OAK-7233.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
