[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768151#comment-15768151 ]
Dominik Süß commented on SLING-6187: ------------------------------------ Do we really want the request to define the PostProcessors? in my mind PostProcessing is an implementation detail that should not be wired to the request. When I was analyzing PostProcessors some years ago I always had the impression that we would probably need to have a better registry of postprocessing pipelines/chains and would make sure every step in the defined pipeline (e.g. registered for a certain path or resourcetype) would need to be satisfied. So instead of dynamically wiring postprocessors that are available by their service ranking we would have a defined pipeline naming steps where the postprocessors would provide the implementation for the steps and none of the steps can be unsatisfied (or would lead to implicit failure). > Provide a way for a POST request to assert a set of required > SlingPostProcessors > -------------------------------------------------------------------------------- > > Key: SLING-6187 > URL: https://issues.apache.org/jira/browse/SLING-6187 > Project: Sling > Issue Type: Improvement > Components: Servlets > Reporter: Justin Edelson > Assignee: Justin Edelson > Fix For: Servlets Post 2.3.16 > > Attachments: SLING-6187-profile.diff, SLING-6187-profile.diff, > SLING-6187-validating.diff, SLING-6187.patch > > > I would like to add support for a new "special" request parameter understood > by the Sling Post Servlet named {{:requiredPostProcessors}}. This parameter > may contain a comma-delimited list of names (see below) which *must* be > available *at the time the request is processed* in order for the request to > be handled. Whether or not those processors _do_ anything or whether the > request succeeds or not is a separate question; this is just a preflight > check if you will. > If any of the required SlingPostProcessors are not available, the request > will fail with a 501 error. > The name of a SlingPostProcessor will be defined by a newly defined service > registration property {{postProcessor.name}} and default to the simple name > of the SlingPostProcessor's implementation class if that property is not > defined. -- This message was sent by Atlassian JIRA (v6.3.4#6332)