1 Reply Latest reply on May 29, 2007 4:44 AM by Ilya Shaikovsky

    a4j makes errors unable to be displayed?

    Thai Dang Vu Apprentice

      My environment: jsf RI 1.2 p02, facelets 1.1.12, tomcat 6.0, a4j & richfaces from the richfaces 3.0.1 snapshot on May 29.

      <h:form id="singlePageForm">
       <table cellspacing="3">
       <td style="font-weight: bold;" valign="top">Archive - From Date: (MM-DD-YYYY)</td>
       <h:inputText id="archiveDate" value="#{singlePage.archiveDate}"
       label="Archive Date">
       <f:convertDateTime pattern="MM-dd-yyyy" />
       <h:message for="archiveDate" style="color: red;"/>
       <a4j:commandButton value="Submit" action="#{singlePage.searchBook}"/>
      If I use a4j:commandButton, then I see this message in tomcat log
      INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
      sourceId=singlePageForm:archiveDate[severity=(ERROR 2), summary=(Archive Date: 'g' could not be understood as a date.), detail=(Archive Date: 'g' could not be understood as a date. Example: 05-29-2007 )]
      and no error message can be seen on the web browser.If I use h:commandButton, I can see the error message on the web browser.
      You can test it with this war file http://download.yousendit.com/1C82261C4B304D7D.
      http://your.machine/dms-cr-08/singlepage.jsf and http://your.machine/dms-cr-08/singplepage-a4j.jsf

      How can I see the error message if I use a4j:commandButton?