Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
Rewriter 1.3.10
-
None
-
None
-
None
Description
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).
Attachments
Issue Links
- is broken by
-
SLING-11103 Improvements in synchronization and additional logging for TransformerFactoryServiceTracker in sling rewriter
- Closed
- relates to
-
SLING-12246 Support Event.NODE_MOVED in JcrResourceListener
- Resolved
-
SLING-6066 Clarify and complete removal resource events
- Closed