No argument there. But like any respectable programmer, I am lazy. ;-)
I'm using a framework to take the drudgery out of web programming.
Do I have to add disabling code for every request-sending widget?
If the answer is yes then ... this is why I have not done it!
(When a client has requested d
And where exactly does the "user experience" fit in to all of this cool
server side trickery? I mean, even in a basic swing application I would
disable input on things people aren't allowed to use when I'm doing
something that will potentially take a long time to complete.
The browser is your fri
IMO, disabling a submit with javascript is a hack. The problem is common,
and a natural consequence of using Tapestry to develop a web application.
Tapestry should be taking care of it for us.
In any case, this can be solved in the same way that the old "locked after
a commit()" errors in T3 were
The filter solution does use a unique token on the form and you can disable
the filter by not including the token on a form. I did have to add logic to
the posted solution to handle errors but even with that code included the
code seems to be non-invasive -- all it does is check for form variable
That seems like a complex solution to the problem which does things in
a filter, where it might be difficult to predict side effects or
override the behaviour in certain circumstances. I'd be more inclined
to implement a unique token solution in a base page class so that I
could overload it in ce
Is there a non-javascript solution to this problem? I have been
experimenting with code based on the forum post below. Has anyone developed
a solution for Tapestry? I propose some sort of consensus should
be reached as to what the best method is to handle double submits and a
patch should be ma
I was looking for a sledgehammer to crack a nut. That's how I ended up
doing it (after spending the day looking for an enterprisey solution!)
Thanks
Denis
Jesse Kuhnert wrote:
Why don't you just disable the submit buttons in question when they submit?
(set the disabled attribute to true)
On 11
Why don't you just disable the submit buttons in question when they submit?
(set the disabled attribute to true)
On 11/15/06, Denis McCarthy <[EMAIL PROTECTED]> wrote:
Hi,
I'm encountering a problem in my app where users are double submitting a
form, creating a hibernate exception in the back
