On 3/27/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> Session-scoped data allows you to navigate to any action keeping
> application state, so you don't need to obey an artificial page flow.
> I think this is a benefit usage-wise.
>
> I prefer to use session-scoped ActionForms and to put every
another approach to handle session scoped objects is to create a filter that
will be responsible to clean up any session scope objects when they are not
needed. Alternatively you can also overwrite the RequestProcessor
processPreprocess method and do session cleaning there as well.
If you want str
On 3/27/06, Chris Cheshire <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a design issue based around form submission, protecting against
> resubmission etc.
>
> I have seen a couple of design "guidelines" that seem to conflict.
>
> 1) Use the session as little as possible (memory issues etc)
> 2) Use
You can use tokens within the Action classes to help prevent multiple
submits. Take a look at the Action Servlet Java Doc for the following
methods:
isTokenValid( request )
resetToken( request )
saveToken( request )
We are using tokens in our app right now. We do something like the
following:
4 matches
Mail list logo