[
https://issues.apache.org/jira/browse/JCRVLT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196642#comment-14196642
]
Marius Petria commented on JCRVLT-71:
-------------------------------------
Regular content has this property, that it can be installed even if the parent
is not present in the target repo. This is a useful property because the
success of the installation does not depend on the state of the target repo. In
particular for a synchronization mechanism based on events it allows good
functioning also in the case of missordered events, i.e. if the profile
creation event is processed before the user creation event.
> Allow creation of ancestor user nodes when they are not explicitly included
> in a filter
> ---------------------------------------------------------------------------------------
>
> Key: JCRVLT-71
> URL: https://issues.apache.org/jira/browse/JCRVLT-71
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Reporter: Marius Petria
> Priority: Minor
>
> JCRVLT-64 restricted the creation of user nodes only to the case when they
> are explicitly included in the filter. This is in practice more secure but
> one should also have the option to lower this guard and be more robust.
> The use case I have in mind is creating exact replicas of user content in two
> instances. There is no security concern that users are autocreated as in the
> end the goal is to have identical instances.
> We could have an option to allow autocreation of user nodes as this will make
> user creation more aligned with regular node creation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
