Cool solution. +1

At 07:03 AM 6/21/2004, Hookom, Jacob wrote:
Sorry, I mean write out a no cache http header... (too early in the
morning).

-----Original Message-----
From: Hookom, Jacob [mailto:[EMAIL PROTECTED]
Sent: Monday, June 21, 2004 8:41 AM
To: 'Struts Users Mailing List'
Subject: RE: How to handle refresh

Create two actions, a list action and a save action.



In both cases, write out an no refresh http header - see Struts Config
documentation for the controller element.



When a user clicks save, post the data and on success or fail, REDIRECT to
the list action.  Then if they refresh, they will be refreshing the list
action.



Jacob Hookom

Senior Analyst/Programmer

McKesson Medical-Surgical



-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, June 21, 2004 1:23 AM
To: Struts Users Mailing List
Subject: How to handle refresh




Hi all,

          We wish to customise the behaviour of IE refresh by just making it
fetch the latest data from the db.
          It works fine in list and edit screens where the last action was a
fetch.
          But if the user has previously saved a record, refresh causes the
save action to be executed once again, contrary to what we wish to achieve.
          Is there any way in which we customise this behaviour?


TIA,

Suhash


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



Reply via email to