3 Replies Latest reply on Jul 20, 2006 6:13 PM by Gavin King

    Double click handling

    ryan dewell Novice

      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?