[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745497#comment-15745497 ] 

Bertrand Delacretaz commented on SLING-6187:
--------------------------------------------

Sorry for chiming in late, just saw this now - how about using a different operation name to point to a specific list of post processors?

I.e. instead of using {{myop}} use {{myop+myflavor}} where "myflavor" is a parameter for a configurable service that checks that all required post processors for "myflavor" are present.

I think what's triggering alarms is pointing directly to a list of post processors, instead of a more abstract concept like "the processors required to do X".

> 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.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)