My impression was that ActionComponent executed the action via an action proxy (although I'm looking at trunk).
But the <s:action...> tag is in a JSP page that will have already been writing, at which point I don't think you'd be able to modify the headers (I've never used response.reset, I don't know if that would help or not). Dave --- On Sat, 6/14/08, Jeromy Evans <[EMAIL PROTECTED]> wrote: > From: Jeromy Evans <[EMAIL PROTECTED]> > Subject: Re: Response already committed when using ActionTag > To: "Struts Users Mailing List" <user@struts.apache.org> > Date: Saturday, June 14, 2008, 10:01 PM > [EMAIL PROTECTED] wrote: > > Hi Jeromy, thanks for the respose. > > > > The response is already committed in the action class > (before the Result is > > executed). In the execute() method, the result of > 'response.isCommitted()' > > is true. So I think the response is committed even > before getting to the > > Result. > > > > According to J2EE documentation, when using > > RequestDispatcher.include(rquest, response), you > can't set headers in the > > response, which means you can't set cookies. > That's the problem I'm having > > - I can't set a cookie in the action class called > via s:action. So perhaps > > that's what s:action does, it does an include. > > > > > > David > > > Okay, that makes sense. I didn't think it did an > include though as that > was this tag's main distinction from the include tag > (in that it invokes > an action directly). But as you're already within a > result (rendering > JSP) perhaps the parent result has already prevented you > from setting > the headers? > > > > > --------------------------------------------------------------------- > 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]
