Hi Leon.
I did what you mentioned as the second approach and used a token
(precisely: locking mechanism, because in my case it's not delete but
edit) to avoid F5 problems. But I'm not happy with that, because, you
already said that, the user sees edit.do in the URL and not view.do,
but view.do
Bernd Schiffer wrote:
Hi Leon.
I did what you mentioned as the second approach and used a token
(precisely: locking mechanism, because in my case it's not delete
but edit) to avoid F5 problems. But I'm not happy with that,
because, you already said that, the user sees edit.do in the URL and
On Wed, 2005-03-23 at 09:20 -0500, Brandon Mercer wrote:
This was exactly the second approach, the redirect approach :-)
Leon
You could forward to a list action. Something like this maybe.
global-forwards
forward name=users path=users.html redirect=true/
/global-forwards
Hi,
I have a problem which I think is common to many of the developers one the
list, and where I'd like to hark to your opinions / solutions.
I think it's a common use case in web applications, where you have to
present a list of something, lets say a list of bikes.
You have normally some
Mailing List'
Subject: The F5 problem - Best Practice (ActionHierarchy)
Hi,
I have a problem which I think is common to many of the developers one the
list, and where I'd like to hark to your opinions / solutions.
I think it's a common use case in web applications, where you have to
present a list
--- Original Message ---
From: Leon Rosenberg [EMAIL PROTECTED]
To: 'Struts Users Mailing List' user@struts.apache.org
Cc:
Sent: Wed 3/23/05 8:32 AM EST
Subject: The F5 problem - Best Practice (ActionHierarchy)
Hi,
I have a problem which I think is common to many of the developers
6 matches
Mail list logo