Ah, thanks for clearing that up.
In my case the processing has to be done once and only once, so
setEnabled(true) need not be called. After successful processing
setResponsePage(..) is called. So this should still work just for me,
right? I'll try tomorrow. If that doesn't work, I'll look at JS
On Mon, 11 Feb 2008, Johan Compagner wrote:
> this code doesn't work at all.
Ah, thanks for clearing that out :)
The nth rule of the Internets: to find a working solution,
post a wrong solution.
Best wishes,
Timo
--
Timo Rantalaiho
Reaktor Innovations Oyhttp://www.ri.fi/ >
those are serverside solutions
and thats not the problem here. They are already one after each other in
wicket (in one session)
johan
On Feb 11, 2008 11:37 AM, C. Bergström <[EMAIL PROTECTED]> wrote:
> Haven't read the entire thread, but based on a best guess.. Would this
> be helpful in some
Haven't read the entire thread, but based on a best guess.. Would this
be helpful in some way?
http://blogs.webtide.com/gregw/2006/10/18/116112750.html
Throttling filter
http://jetty.mortbay.org/xref/org/mortbay/servlet/ThrottlingFilter.html
./C
--
this code doesn't work at all.
the onclick method isn't called at the same time by 2 request (2 link
clicks)
They are synchronized by wicket itself.
So what happens with the code below is that the first request sets the
enabled to false
then does the processing, then wicket blocks the second requ
Martijn Dashorst wrote:
On 2/7/08, Matthijs Wensveen <[EMAIL PROTECTED]> wrote:
The if(!isEnabled()) will happen though, because the link is not really
disabled on the client side, but it does prevent
doSomeHeavyWeightProcessing to be called the second time which is what I
need.
The pr
On 2/7/08, Matthijs Wensveen <[EMAIL PROTECTED]> wrote:
> The if(!isEnabled()) will happen though, because the link is not really
> disabled on the client side, but it does prevent
> doSomeHeavyWeightProcessing to be called the second time which is what I
> need.
The problem is that the href of th
Hi,
The if(!isEnabled()) will happen though, because the link is not really
disabled on the client side, but it does prevent
doSomeHeavyWeightProcessing to be called the second time which is what I
need.
What are the pros / cons of (ab)using setEnabled for this instead of
just a member variab
there is a mask component in wicketstuff-minis. you can write a call
decorator that will bring up the mask that will cover the whole screen
and prevent the user from clicking.
-igor
On Feb 6, 2008 4:37 AM, Matthijs Wensveen <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a Link (not Ajax) on a co
On Wed, 06 Feb 2008, Matthijs Wensveen wrote:
> I have a Link (not Ajax) on a component that does some heavyweight
> processing in onClick. During this processing I want to block other
> clicks from the same user. Is there a generic way to block multiple
> requests on the same link? I would pref
Matthijs Wensveen wrote:
Hello,
I have a Link (not Ajax) on a component that does some heavyweight
processing in onClick. During this processing I want to block other
clicks from the same user. Is there a generic way to block multiple
requests on the same link?
I would prefer a solution wit
Hello,
I have a Link (not Ajax) on a component that does some heavyweight
processing in onClick. During this processing I want to block other
clicks from the same user. Is there a generic way to block multiple
requests on the same link? I would prefer a solution without Ajax /
JavaScript, but
12 matches
Mail list logo
