[jira] [Commented] (SLING-12245) Sling Rewriter does not detect configuration changes coming in via move

["Konrad Windszus (Jira)" <ji...@apache.org>]

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

Konrad Windszus commented on SLING-12245:
-----------------------------------------

I added some tests in https://github.com/apache/sling-org-apache-sling-jcr-resource/commit/7660582019bc8b4b0fdda73bdddbde77262159e6 which outline the current behaviour.

> Sling Rewriter does not detect configuration changes coming in via move
> -----------------------------------------------------------------------
>
>                 Key: SLING-12245
>                 URL: https://issues.apache.org/jira/browse/SLING-12245
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: Rewriter 1.3.10
>            Reporter: Konrad Windszus
>            Priority: Major
>
> If one renames/moves a JCR node from {{/apps/my/config/invalid-rewriter}} to {{/apps/my/config/rewriter}} the new rewriter configuration is not being detected by the {{ProcessorManagerImpl}} due to the {{ResourceChangeListener}} only being configured to listen for changes below the {{rewriter}} resource (https://github.com/apache/sling-org-apache-sling-rewriter/blob/4d1952648e35e7001236f282040a78479f7726d4/src/main/java/org/apache/sling/rewriter/impl/ProcessorManagerImpl.java#L69).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)