> So we are consistent on the 'state' flag names like -used-
> Bug 18022, talked about wrapping the ActionForm
> with another class when it was returned from the createActionForm
> method.
> It would have two attributes: -recycled-, and ActionForm.
>
> It would be nice if the terms -used-, and
> -Original Message-
> From: David Graham [mailto:[EMAIL PROTECTED]
...
>
> This seems more responsive than a periodic cleanup and we wouldn't have to
> cache HttpSession objects which may not be safe/legal. Also, I think
> placing the cleanup in the RequestProcessor guarantees that it is
David Graham wrote:
--- Robert Leland <[EMAIL PROTECTED]> wrote:
Use Cases: I am not familar with the particular use cases where the
ActionMessage needs
to hang around in the session. So these suggestions might not fit.
The main reason I've seen on the user list (and the reason I need it
--- Robert Leland <[EMAIL PROTECTED]> wrote:
> Use Cases: I am not familar with the particular use cases where the
> ActionMessage needs
> to hang around in the session. So these suggestions might not fit.
The main reason I've seen on the user list (and the reason I need it) is
to redirect to a
It does come up, especially when people are using frames. I usually
recommend that people use an Action to cache the messages in the session
during the redirect and then have another Action to move it back again
afterwards. It might be possible to engineer a standard Action to
automate this sor
Use Cases: I am not familar with the particular use cases where the
ActionMessage needs
to hang around in the session. So these suggestions might not fit.
Questions:
Would managing the life cycle through the struts-config.xml, like the
ActionForm work ?
or
How about a PlugIn that has the ability
