The solution is thread safe - as it uses tapestry's own property management.
I've yet to see it fail! I'm still cleaning code up so I'll supply it soon.
Oh yes, and - I am a cheat - the component is a copy & paste of the original
form with about 10-20 lines (spaces included!) of extra code.
On 11/
Question: does Tap use component pooling, like it does for pages?
When you lock form submission and page visiting does it block other
concurrent accesses from other users to the same page and form?
If your form concurrency's sound and safe, I find it's a really
interesting solution, could you se
; -Original Message-
> From: Patrick Casey [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 30, 2005 6:15 PM
> To: 'Tapestry users'
> Subject: RE: Preventing multiple form submission within Tapestry
>
>
> This ought to work:
>
> Step 1:
: 'Tapestry users'
Subject: RE: Preventing multiple form submission within Tapestry
This ought to work:
Step 1: Synchronize your servlet.doService() on the HttpSession
so
that two user requests will never run in parallel.
Step 2: Add a hidden, monotonically increasi
Ralph Johnston wrote:
We're trying to prevent redirecting to a page that we don't want the user to go to.
Granted, they might learn after they get the exception page a couple of times and
stop doing multiple submissions, that just isn't a very user friendly way of handling
this issue.
What
We're trying to prevent redirecting to a page that we don't want the user to go
to.
Granted, they might learn after they get the exception page a couple of times
and
stop doing multiple submissions, that just isn't a very user friendly way of
handling
this issue.
What we need to do is find
Throw a PageRedirectException and redirect to your confirmation
page.
Pat
> -Original Message-
> From: Ralph Johnston [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 30, 2005 8:11 PM
> To: Tapestry users
> Subject: Re: Preventing multiple form su
Tom,
Thanks for the reply. That is pretty much what we are doing, but how do we
reject
the extra submissions? If we just return from the listener method on
subsequent
calls, then the user sees the same page, instead of the confirmation page.
Thanks!
> Ralph Johnston wrote:
> > Hi, we're wo
Hi.
Like Pat says, you need to synchronize/serialize your requests somehow.
I use a modified RequestControlFilter, originally from:
http://www.onjava.com/pub/a/onjava/2004/03/24/loadcontrol.html?page=1
You also need to prevent multiple submissions server-side.
I use a variation on the FlowSynchr
Ralph Johnston wrote:
Hi, we're working on a project in which we need to submit a form which then creates
a record in a database on successful submission. The problem we have is that if
someone clicks on the submit button more than once, it creates duplicate records of
the record that the p
This ought to work:
Step 1: Synchronize your servlet.doService() on the HttpSession so
that two user requests will never run in parallel.
Step 2: Add a hidden, monotonically increasing (like a static
incrementer) hidden value to the form in question.
Step 3: Add a
11 matches
Mail list logo
