You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Marc Pfaff (JIRA)" <ji...@apache.org> on 2016/01/15 11:27:39 UTC

[jira] [Commented] (SLING-5371) Improving JcrInstaller's move listener registration

    [ https://issues.apache.org/jira/browse/SLING-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101589#comment-15101589 ] 

Marc Pfaff commented on SLING-5371:
-----------------------------------

[~cziegeler], [~bdelacretaz]: What do you think about the provided patches? Does that make sense to you?

> Improving JcrInstaller's move listener registration
> ---------------------------------------------------
>
>                 Key: SLING-5371
>                 URL: https://issues.apache.org/jira/browse/SLING-5371
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>            Reporter: Marc Pfaff
>         Attachments: SLING_5371.patch, SLING_5371_jackrabbit.patch, SLING_5371_jcr_only.patch
>
>
> The JcrInstaller is currently registering a JCR listener for move events on the root node with setting the 'deep' property to true. If it comes to processing the underlaying Oak observation queue, this combination is very inefficient, as it does not allow Oak to filter changes by path. 
> AFAIU this move listener is covering the use case where an installer artifact is moved from/to an installer root folder. I therefore wanted to propose to register the move listener on the configured root folders only.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)