Hi there,
I think this has been already discussed in the past on this list. Several
solutions have been discussed, mainly using a token mechanism + interceptor.
I don't have time yet to dig for info, but for sure this is something I'd
like to have as a core feature if possible. This is clearly a
Hi Nikolaos,
have you used the transaction token mechanism in Struts? A similar mechanism
should solve your problem. It would be really easy to implement. If you
don't know what I am talking about, let me know and I will explain further.
Cheers,
Angel.
Nikolaos Giannopoulos wrote:
>
> Hi,
>
On 16-11-2010 at 19:43, Newman, John W wrote:
> Is the token universally good for any http based application or am I
> missing something? Any reason you would NOT want this feature in your app?
> Obviously it could be flagged disabled, possibly even by default.
In general, I don't think it would
be
flagged disabled, possibly even by default.
-Original Message-
From: Stone, Timothy [mailto:tst...@barclaycardus.com]
Sent: Tuesday, November 16, 2010 2:11 PM
To: Stripes Users List
Subject: Re: [Stripes-users] Preventing multiple form submission
Struts 1.x provides this fu
ge-
From: Newman, John W [mailto:john.new...@viaoncology.com]
Sent: Tuesday, November 16, 2010 1:35 PM
To: Stripes Users List; nikol...@brightminds.org
Subject: Re: [Stripes-users] Preventing multiple form submission
I'm wondering why the stripes form tag and stripes filter don't p
Sent: Tuesday, November 16, 2010 10:35 AM
To: nikol...@brightminds.org; Stripes Users List
Subject: Re: [Stripes-users] Preventing multiple form submission
On 16-11-2010 at 10:17, Nikolaos Giannopoulos wrote:
> Just wondering how others elegantly solve this situation:
>
> 1) User is e
I usually do that on the client side:
document.getElementById("submitButton").onclick = function(e) {
e.preventDefault();
this.disabled = true;
this.form.submit();
};
But if the user presses the stop button before the response is returned, he
will have to refresh the page in order to
On 16-11-2010 at 10:17, Nikolaos Giannopoulos wrote:
> Just wondering how others elegantly solve this situation:
>
> 1) User is editing a form and fills it out and clicks submit button
> 2) Form gets successfully processed on the server however before a
> response is returned the user hits the st
Hi,
Just wondering how others elegantly solve this situation:
1) User is editing a form and fills it out and clicks submit button
2) Form gets successfully processed on the server however before a
response is returned the user hits the stop button, their internet
connection drops, etc...
4) Use