Thanks Adrian,

 

For option 1 I have the following doubt:

1.      What exactly are my requirements in order to use the s:token
component from shale, is there some documentation on this integration?  I
just want that component and nothing more from shale, is there like a
reduced library and simplified integration mechanism…I’d really like to
reduce my dependencies with other frameworks as much as possible.

For option 2 I have the following doubts:

1.      Does this solution that you posted work with Facelets too?
2.      Would there be some considerable performance issues on implementing
this approach?  I see that it affects all forms rendered on the application…

 

Regards and thanks again,

JV

 

  _____  

De: Adrian Mitev [mailto:[EMAIL PROTECTED] 
Enviado el: jueves, 03 de mayo de 2007 16:13
Para: MyFaces Discussion
Asunto: Re: double click issue in Firefox...

 

To prevent the double submit you could use a server side solution like the
token synchronizer pattern implemented as a shale component called s:token
from shale-core lib that you can get from here [1] or to implement it
yourself [2] 

[1] http://shale.apache.org/
[2] http://jroller.com/page/mert?entry=jsf_preventing_double_form_submit 

2007/5/3, Jorge Vásquez <[EMAIL PROTECTED]>:

Regards to all,

During some testing I found that some unpredictable errors occur with
Firefox whenever a user clicks twice rapidly either on a commandLink or on a
commandButton.  What happens is that the respective method modifies some
internal state the first time but then when it gets executed again it founds
inconsistencies that cause an exception to be thrown.  Adding exception
controls to each method for this very specific scenario would result
terribly cumbersome, so I am writing to see if somebody out there has had a
similar problem and how have you managed to solve it.  I played the other
day for a while with JavaScript events but unfortunately those double click
events are uncontrollable when there's also the presence of onclick events,
since most of the time double clicks are also interpreted as simple clicks
and that turns out to be a huge chaos.  

I also tested this behaviour in IE7 (for which I must say that at last
Microsoft launched a descent browser) and there's no problem.  Apparently
this browser blocks double clicks.

Thanks in advance to anybody that could give me some advice…

JV

 

 

Reply via email to