Hello,
we have a struts application with this constraints:
- view rendering could be dependent on request scope
attributes;
- ActionForward used after successful action does
*not* define redirect="true";
- Modifying our struts application is not an option.
In this scenario execution of a second RenderRequest
will call the action again without any request
parameter.
How can we use the Struts Bridge to make our
application portlet-compliant ?
In our opinion a possible solution could be to modify
the Struts Bridge to preserve the StrutsRenderContext
until the next ActionRequest, instead of removing it
from session after the first RenderRequest.
In this way RenderRequest behaviour is preserved for
all following RenderRequest call.
We understand that this is in contrast with the Struts
Bridge philosophy, though.
Is there any other solutions to this problem?
BTW the definition of the attribute keep="true" in the
struts-portlet-config.xml for the request attributes
we want to preserve does not seem to work in our
scenario.
Thank you for your attention.
Regards
Max
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
