On 31.01.11 18:13, "Julian Sedding" <[email protected]> wrote:
>What about taking up the discussion about a PreProcessor interface as
>a hook into the post servlet? This was considered and discarded in
>SLING-594. This seems to be a use-case, which could be solved using a
>PreProcessor (essentially, this would allow the @Patch feature to be
>implemented outside of Sling).
The question is how this would look like: the PreProcessor must be able to
work on the jcr session and fill the list of changes (possible with the
proposed PreProcessor interface, see below) but also to stop the standard
operation to use certain request parameters.
The latter is not really possible... one must be able to remove certain
parameters from the request or from the RequestProperty list to do so.
Maybe the collecting of the RequestProperty map is done before the
PreProcessors are called and they can modify the map?
interface PreProcessor {
void process(SlingHttpServletRequest, List<Change>);
}
Regards,
Alex
--
Alexander Klimetschek
Developer // Adobe (Day) // Berlin - Basel
