[SLING-12085] Add a RequestPreprocessor SPI to support path mappings in distribution messages

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Content Distribution
• Assignee: Unassigned
• Reporter: Dirk Rudolph
• Created: 09/Oct/23 10:49
• Updated: 09/Oct/23 10:49

Description

We have a use case where the target system of Sling Content Distribution has a different content structure / path names than the origin system. 

To support this we would like to propose the addition of a RequestPreprocessor SPI that allows us to apply a path mapping to the objects contained in a distribution messages. 

This SPI should be used in the journal based distribution implementation.