Well it looks like I've found the cause of the problem. The ServletResponse object passed into my Controller's execute is wrapped inside of ServletResponseWrapperInclude, which wraps an instance of org.apache.catalina.core.ApplicationHttpResponse. In that class, the addCookie() method is overidden and ignores any attempt to change a header - in my case, a cookie.
Does anybody have any experience with this? Should I just move the cookie setting into an action? Is this a problem I will only see in Tomcat (since ApplicationHttpResponse is in a catalina package)? Is there some kind of workaround? Thanks again for all your help. On 2/21/06, brian papa <[EMAIL PROTECTED]> wrote: > Oops, meant to question the presence of the Response there. > > On 2/21/06, Dave Newton <[EMAIL PROTECTED]> wrote: > > brian papa wrote: > > > I'm starting to think now that perhaps I'm doing this in the wrong > > > place. After all the purpose of a controller should simply be to > > > prepare data for rendering in a JSP tile. I'm wondering though if this > > > is the case what the purpose is of having the HttpServletRequest as a > > > parameter to a Controller? > > > > > So you can put the data you just prepared into the request for rendering > > in a JSP tile? > > > > ;) > > > > Dave > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
