FWIW, as a Sling newcomer I got tripped up by the same code in Sling's
RequestData class when I tried to mix in some request parameters in the
usual way. This seemed to put a sizable dent in the usefulness of
SlingHttpServletRequestWrapper, but I didn't have time to pursue the
matter then.
Best,
Ray
On 1/8/10 7:31 AM, Ian Boston wrote:
We have been trying to implement a Batch method processor (ie a servlet that
performs multiple requests batching the responses up into a single
request/response) in Sling.
Normally with servlets this would require
requestDispacher.forward(wrappedRequest, wrappedResponse) but this doent work
since Sling unwrapps all request back to a internal SlingHttpServletRequestImpl
object so although you can get hold of the requestDispatcher, and call the
forward method, its almost pointless.
Whats the right way of doing this sort of thing in Sling ?
Ian
BTW, we have also tried Filters registered against the SlingMainSevlet (via
OSGI), adding another top level servlet directly to the httpservice and adding
filters at the http service level before the SlingMainServlet. None appear to
work for all sorts of reason, sadly perfectly valid and to spec.
