On Thu, Aug 26, 2010 at 14:47, Felix Meschberger <[email protected]> wrote: > Hi, > > What is the exact use case ?
Have some servlet create something, but then use the standardized sling post request "syntax" to add additional unstructured data. > Could it be solved by your servlet handling part of the post, and for > example create a request wrapper which exposes modified parameters. That > servlet could then forward to the default POST servlet for final processing. Then the servlet looses a lot of control: - response handling - what operations are allowed to run That could be handled, but only be complex logic where the servlet has to inspect the parameters, complex response wrappers, etc. The nice thing is that the SlingPostOperation interface is there, ready to use... why not? > As such I am currently opposed to exporting the internal operations. Then making all of them services (2) is the way to go. I probably could also have a SlingPostOperation myself, instead of the servlet, but that one couldn't make use of all the built-in logic of the existing operations. Regards, Alex -- Alexander Klimetschek [email protected]
