[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]
