You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robin KM (Jira)" <ji...@apache.org> on 2021/01/29 06:21:00 UTC
[jira] [Updated] (SLING-10101) Sequence of instructions is not
always respected
[ https://issues.apache.org/jira/browse/SLING-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robin KM updated SLING-10101:
-----------------------------
Description:
Sling Repoinit doesn't always seem to respect the sequence of statements specified in a configuration file.
For example:
{code:java}
create group Group_A
create group Group_B
set ACL for Group_A
allow jcr:read on /content
deny jcr:write on /content/example
end
set ACL for Group_B
allow jcr:read on /var
deny jcr:write on /var/example
end
delete group Group_A
delete group Group_B
{code}
In the above example, overall execution of script fails because the creation and deletion of groups happens first and only then the 'set ACL' instructions are attempted and they're unable to find the Authorizable.
Not sure if this is a timing / sync issue when the statements are executed or because of the design which takes into account the 'type' of statements.
was:
Sling Repoinit doesn't always seem to respect the sequence of statements specified in a configuration file.
For example:
{code:java}
create group Group_A
create group Group_B
set ACL for Group_A
allow jcr:read on /content
deny jcr:write on /content/example
end
set ACL for Group_B
allow jcr:read on /var
deny jcr:write on /var/example
end
delete group Group_A
delete group Group_B
{code}
In the above example, overall execution of script fails because the creation and deletion of groups happens first and only then the set ACL instructions are attempted and they're unable to find the Authorizable.
Not sure if this is a timing / sync issue when the statements are executed or because of the design which takes into account the 'type' of statements.
> Sequence of instructions is not always respected
> ------------------------------------------------
>
> Key: SLING-10101
> URL: https://issues.apache.org/jira/browse/SLING-10101
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Affects Versions: Repoinit Parser 1.6.2, Repoinit JCR 1.1.28
> Reporter: Robin KM
> Priority: Major
>
> Sling Repoinit doesn't always seem to respect the sequence of statements specified in a configuration file.
> For example:
> {code:java}
> create group Group_A
> create group Group_B
> set ACL for Group_A
> allow jcr:read on /content
> deny jcr:write on /content/example
> end
> set ACL for Group_B
> allow jcr:read on /var
> deny jcr:write on /var/example
> end
> delete group Group_A
> delete group Group_B
> {code}
>
> In the above example, overall execution of script fails because the creation and deletion of groups happens first and only then the 'set ACL' instructions are attempted and they're unable to find the Authorizable.
>
> Not sure if this is a timing / sync issue when the statements are executed or because of the design which takes into account the 'type' of statements.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)