You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/02/07 10:58:00 UTC
[jira] [Comment Edited] (SLING-12245) Sling Rewriter does not detect configuration changes coming in via move
[ https://issues.apache.org/jira/browse/SLING-12245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815241#comment-17815241 ]
Konrad Windszus edited comment on SLING-12245 at 2/7/24 10:57 AM:
------------------------------------------------------------------
According to SLING-6066 {{REMOVED}} events are already considered for parent's of the listener path. But it seems {{ADDED}} are not. [~cziegeler] Can you point me the code which implements the handling of {{REMOVED}} for listener's parent paths?
was (Author: kwin):
According to SLING-6066 `REMOVED` events are already considered for parent's of the listener path. But it seems `ADDED` are not. [~cziegeler] Can you point me the code which implements the handling of `REMOVED` for listener's parent paths?
> 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)