Re: ServletResponseAware - request can be null?

2013-07-08 Thread Christian Grobmeier
On Mon, Jul 8, 2013 at 9:42 PM, Paul Benedict wrote: > Do this test. Put a breakpoint in the setter that is storing the response. > You either have the case where the interceptor is not being fired (and thus > your method is not being called) or you have found a null somehow being > passed in. I b

Re: ServletResponseAware - request can be null?

2013-07-08 Thread Paul Benedict
Do this test. Put a breakpoint in the setter that is storing the response. You either have the case where the interceptor is not being fired (and thus your method is not being called) or you have found a null somehow being passed in. I bet the former is the case, but you'll have to test to find out

Re: ServletResponseAware - request can be null?

2013-07-08 Thread Lukasz Lenart
2013/7/5 Christian Grobmeier : > I am implementing the ServletResponseAware interface and found out > that sometimes the HttpServletResponse is null when I execute() the > action. > > ServletConfigInterceptor is definitely executed before. Actually often > the HttpServletResponse is not null and my

ServletResponseAware - request can be null?

2013-07-05 Thread Christian Grobmeier
Hi, I am implementing the ServletResponseAware interface and found out that sometimes the HttpServletResponse is null when I execute() the action. ServletConfigInterceptor is definitely executed before. Actually often the HttpServletResponse is not null and my code seems to work. Not sure if I s