...
[14:53:31 CDT(-0500)] <drewwills> that's too bad... if we could use a completely custom ServletResponse it would have the additional benefit of allowing us to remove the response as a parameter on the method call
[14:54:34 CDT(-0500)] <drewwills> i suppose adding ServletContext as a parameter makes the most sense, though it stinks that a ton of invocations will look like: invoke(req.getSession().getServletContext(), req, res, ...);
[14:55:00 CDT(-0500)] <EricDalquist> yes but you don't do req.getSession.getServletContext
[14:55:06 CDT(-0500)] <EricDalquist> in spring you implement ServletContextAware
[14:55:09 CDT(-0500)] <drewwills> i might in a client
[14:55:11 CDT(-0500)] <EricDalquist> and have it injected in your class
[14:55:14 CDT(-0500)] <EricDalquist> right
[14:55:21 CDT(-0500)] <drewwills> if you're a controller
[14:55:24 CDT(-0500)] <EricDalquist> yup