Double click handling

[rdewell]

In testing, I've noticed that a common user behavior of double clicking a link (backed by a commandLink/commandButton), can easily and often lead to the error:

------------
Caused by: javax.ejb.EJBTransactionRolledbackException: null; CausedByException is:
null; CausedByException is:
Application Error: no concurrent calls on stateful beans
------------

It's obvious why it leads to this error, but I wonder if there is any way for Seam to catch that and only process one of them, avoiding the concurrent calls. Or, maybe this is something left to JSF 1.2 as I hear it deals with postbacks better?

Ryan

[gavin.king]

This was already reported in JIRA, and looks to me like a bug in JBoss EJB3


http://jira.jboss.com/jira/browse/EJBTHREE-313

[ngolovin]

Are there any news on this issue?

The JIRA entry
http://jira.jboss.com/jira/browse/EJBTHREE-313
has been rejected, because concurrent calls on stateful session beans are not allowed by the EJB specification. The double click problem however stays.

Has anybody found a good workaround for this?

I haven't even been able to write a decent error page for the exception, because the behavior is hard to reproduce, and thus the error page is hard to test. Also, the exception which shloud be caught can be different, although the cause is always javax.ejb.EJBException

[gavin.king]

It should be very easy to write an errorpage. The root cause exception is always a ConcurrentAccessException.