[jira] [Resolved] (SLING-6436) Sling Rewriter: Configre rewriter pipeline programmatically

["Justin Edelson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Edelson resolved SLING-6436.
-----------------------------------
    Resolution: Fixed

implemented in r1777332

request attribute name is org.apache.sling.rewriter.pipeline

> Sling Rewriter: Configre rewriter pipeline programmatically 
> ------------------------------------------------------------
>
>                 Key: SLING-6436
>                 URL: https://issues.apache.org/jira/browse/SLING-6436
>             Project: Sling
>          Issue Type: Wish
>          Components: Extensions
>    Affects Versions: Rewriter 1.2.0
>            Reporter: Stefan Grimm
>            Assignee: Justin Edelson
>
> Currently, the rewriter pipeline that is used for processing a request is chosen by some criteria + the order property of each pipeline.
> There are use cases where you know which pipeline to use and don't want to take the risk that another pipeline is chosen unexpectedly, breaking functionality (because it is matching as well as the desired pipeline, but has a higher order).
> So the suggestion is to provide optional means to explicitly specify the rewriter pipeline to use for a request, for example by specifying a request attribute.



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