that SEEMS to be working. It incorporates our solution
to the double submit problem that we used on our JSP's. It didn't appear
to be working for me at first, but seems to be now. (It does use the old
servlet request/session objects, but this may change once all our old code
is upgraded to wicket
The one missing piece from your solution is synchronization. There is the
slightest possibility that the second submit of a double submit could enter
onSubmit before the token is reset. I am not yet sure what would be the best
object to synchronize on, possibly the session id?
Actually
. It incorporates our
solution
to the double submit problem that we used on our JSP's. It didn't
appear
to be working for me at first, but seems to be now. (It does use the
old
servlet request/session objects, but this may change once all our old
code
is upgraded to wicket
Sorry, I should have attributed that code to Joel.
-Original Message-
From: Zappaterrini, Larry [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2008 10:56 AM
To: users@wicket.apache.org
Subject: RE: Double submit problem
I don't have a patch, at this point I was just testing
be the
best
object to synchronize on, possibly the session id?
hillj2 wrote:
Here's a solution that SEEMS to be working. It incorporates our
solution
to the double submit problem that we used on our JSP's. It didn't
appear
to be working for me at first, but seems
onSubmit before the token is reset. I am not yet sure what would be
the
best
object to synchronize on, possibly the session id?
hillj2 wrote:
Here's a solution that SEEMS to be working. It incorporates our
solution
to the double submit problem that we used
sure what would be
the
best
object to synchronize on, possibly the session id?
hillj2 wrote:
Here's a solution that SEEMS to be working. It incorporates our
solution
to the double submit problem that we used on our JSP's. It didn't
to the double submit problem that we used on our JSP's. It
didn't
appear
to be working for me at first, but seems to be now. (It does use
the
old
servlet request/session objects, but this may change once all our
old
code
is upgraded to wicket
to be working. It incorporates
our
solution
to the double submit problem that we used on our JSP's. It
didn't
appear
to be working for me at first, but seems to be now. (It does
use
the
old
servlet request/session objects
to the double submit problem that we used on our JSP's.
It didn't
appear
to be working for me at first, but seems to be now. (It
does use
the
old
servlet request/session objects, but this may change
once all our
old
code
. It
incorporates our
solution
to the double submit problem that we used on our JSP's.
It didn't
appear
to be working for me at first, but seems to be now. (It
does use
the
old
servlet request/session
on, possibly the session id?
hillj2 wrote:
Here's a solution that SEEMS to be working. It
incorporates our
solution
to the double submit problem that we used on our
JSP's.
It didn't
:
Here's a solution that SEEMS to be working. It
incorporates our
solution
to the double submit problem that we used on our
JSP's.
It didn't
appear
to be working for me at first, but seems to be now
:
Here's a solution that SEEMS to be working.
It
incorporates our
solution
to the double submit problem that we used on
our
JSP's.
It didn't
appear
to be working for me at first, but seems
On Tue, Mar 25, 2008 at 1:50 PM, Johan Compagner [EMAIL PROTECTED] wrote:
I dont think this can be easily done by Behaviors or Validators
Only when we make it that a validator can also be a behavior (or provide a
behavior) then that would be possible.
for now Validatiors cant contribute to
wrote:
Here's a solution that SEEMS to be working. It
incorporates our
solution
to the double submit problem that we used on our JSP's.
It didn't
appear
to be working for me at first, but seems to be now. (It
does
to the double submit problem that we used on our JSP's.
It didn't
appear
to be working for me at first, but seems to be now. (It
does use
the
old
servlet request/session objects, but this may change once
all our
Does this stuff here prevent double submit?
http://wicket.apache.org/docs/wicket-1.3.2/wicket/apidocs/org/apache/wicket/settings/IRequestCycleSettings.html
...so that not only form submits are shielded from the double submit
problem...
On Mon, Mar 10, 2008 at 6:56 AM, Joel Hill [EMAIL PROTECTED
://wicket.apache.org/docs/wicket-1.3.2/wicket/apidocs/org/apache/wicket/settings/IRequestCycleSettings.html
...so that not only form submits are shielded from the double submit
problem...
On Mon, Mar 10, 2008 at 6:56 AM, Joel Hill [EMAIL PROTECTED] wrote:
I'm trying to prevent the double
Here's a solution that SEEMS to be working. It incorporates our solution to
the double submit problem that we used on our JSP's. It didn't appear to be
working for me at first, but seems to be now. (It does use the old servlet
request/session objects, but this may change once all our old code
this message in context:
http://www.nabble.com/Double-submit-problem-tp15957979p15976496.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
--
View this message in context:
http://www.nabble.com/Double-submit-problem-tp15957979p15976516.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
onclick=saveForm(this); setIsDocBeingSubmitted(true);
name=submitButtonName value=Save /
--
View this message in context:
http://www.nabble.com/Double-submit-problem-tp15957979p15976673.html
Sent from the Wicket - User mailing list archive at Nabble.com
(true); name=submitButtonName value=Save /
--
View this message in context:
http://www.nabble.com/Double-submit-problem-tp15957979p15988774.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e
:
http://www.nabble.com/Double-submit-problem-tp15957979p15988777.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm trying to prevent the double submit problem, where the user clicks the
submit button more than once causing a double post.
I tried implementing the soluion suggested here:
http://www.nabble.com/Re%3A-double-form-submission-handling---p13850262.html
The problem is if there's a validation
for the second submit).
Martijn
On 3/10/08, Joel Hill [EMAIL PROTECTED] wrote:
I'm trying to prevent the double submit problem, where the user clicks the
submit button more than once causing a double post.
I tried implementing the soluion suggested here:
http://www.nabble.com/Re%3A-double-form
27 matches
Mail list logo
