9 Replies Latest reply on Jul 7, 2008 4:34 AM by Ilya Shaikovsky

    a4j:commandButton problem

    Lotfi Mellouk Master


      I remark this problem after migration to 3.2.1.

      If an expection is thrown after the validation/conversion phase (think on phase 3), example on the action we specify a method that not exist,,
      with a4j button nothing happen, and we can not see the exception using a4j:status show on progress for a long time..
      with h:commandButton we get the exception.

      also, I got the same problem on the 3.2.1.GA version on sessionExpiredExeption, I had to change a4j commandButton to h:commandButton to understand what happens..