Hi, Looking at the current sling-api:
public SlingHttpServletRequestWrapper(SlingHttpServletRequest delegatee) I would have expected public SlingHttpServletRequestWrapper(ServletRequest delegatee) And then the constructor can complain if the delegatee (why not call that simply "wrappedRequest" by the way?) is not of the right type. And the same goes for the response wrapper, of course. What's the rationale for doing things the current way? I'm not against that, just trying to understand the pros and cons. -Bertrand
