[
https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752250#comment-15752250
]
Justin Edelson commented on SLING-6187:
---------------------------------------
bq. IIUC, the new validating patch requires a configuration of the sling post
servlet bundle (for the ModificationValidatingPostProcessor) to set a pattern
(like @Encrypted) that must not be present after all other processors have run
through?
Correct.
bq. If we have a mechanism where the presence of a post processor that
announces its @Suffix in the service properties itself is enough (see above),
that additional configuration wouldn't be necessary. But that would mean all
post processors handling custom suffixes need to be changed, otherwise their
requests would fail.
I'm not sure I understand this. We can't prohibit the @ symbol in the
modification set in general since this is a legal JCR character, as I wrote in
https://issues.apache.org/jira/browse/SLING-6187?focusedCommentId=15606583&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15606583.
And if we rely on the service properties, that doesn't really help if the
service is not present (the original issue).
> 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)
