[
https://issues.apache.org/jira/browse/JCR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780612#action_12780612
]
angela commented on JCR-2399:
-----------------------------
i deliberately didn't set the protected-item-importers as default behavior in
order to keep it the way it
always was in jackrabbit: protected items are ignored upon session/workspace
import xml.
that's way the default is called default btw... the extra stuff should be in
addition. and i considered import
of protected items to be the addition....
> Enable protected security importers by default
> ----------------------------------------------
>
> Key: JCR-2399
> URL: https://issues.apache.org/jira/browse/JCR-2399
> Project: Jackrabbit Content Repository
> Issue Type: Wish
> Components: jackrabbit-core
> Affects Versions: 2.0-beta1
> Reporter: Tobias Bocanegra
> Attachments: default_importers.r882540.patch
>
>
> We added those cool protected property and node importers for enabling
> sysview import of users,groupd and acls. unfortunately, they are only
> enabled when the respective config is set:
> <Import>
> <ProtectedNodeImporter
> class="org.apache.jackrabbit.core.xml.AccessControlImporter"/>
> <ProtectedPropertyImporter
> class="org.apache.jackrabbit.core.security.user.UserImporter">
> <param name="importBehavior" value="besteffort"/>
> </ProtectedPropertyImporter>
> </Import>
> i think we should enable them by default, i.e. for an empty config. if
> someone wants to disable them, they can still reference the default importers:
> <Import>
> <ProtectedNodeImporter
> class="org.apache.jackrabbit.core.xml.DefaultProtectedNodeImporter"/>
> <ProtectedPropertyImporter
> class="org.apache.jackrabbit.core.xml.DefaultProtectedPropertyImporter" />
> </Import>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
