Briefly, - A phaselistener that checks the session for a uniqueToken. If there is none, generates a new one and stores it in session. If there is one, checks the equality of that one with the one submitted with form. - An extended formRenderer that renders the session-scoped-uniqueToken as the hidden field to page.
Of course this approach should be improved for popups and frames ;) Regards, Mert.. On 12/6/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
You could also install a servlet filter that serializes all requests for the same session. There are probably other thread-safety issues when processing multiple requests simulaneously for the same session under JSF 1.1. You'd still need to work through the double-click detection, but it'd be easier if you're assured that no other request is occurring for the session. On 12/6/06, Adrian Mitev <[EMAIL PROTECTED]> wrote: > Shale has component s:token that could handle double submit. > > 2006/12/6, Charbel Abdul-Massih <[EMAIL PROTECTED]>: > > > > > > > > > > What's the best way to handle double clicks on buttons in JSF??? > > > > > > > > Thanks, > > Charbel > >
