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

Alexander Klimetschek commented on SLING-6187:
----------------------------------------------

[~fmeschbe] The problem is if you have an important "add-on" post processor, 
for example one that encrypts properties server side before storing them in the 
JCR, and for some reason it's not active (bundle restarting etc.). Since it's 
"add-on", it would happily store the unprocessed (e.g. unencrypted) value and 
return without an error.

Maybe the source of the issue is the add-on character of such a post processor 
as in the encryption case. If it would be something that does not work at all 
if the post processor (or whatever pluggable interface) is not found, you 
automatically get an error.

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

Reply via email to