Uploaded image for project: 'JBoss WFK 2'
  1. JBoss WFK 2
  2. WFK2-744

<rich:autocomplete required="true"> doesn't validate when using <h:commandLink> and <rich:placeholder> together

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.6.0.GA, 2.7.0.ER1, 2.7.0.ER2
    • Fix Version/s: None
    • Component/s: RichFaces
    • Environment:

      JBoss EAP 6.x up to EAP 6.3.0

    • Target Release:
    • Steps to Reproduce:
      Hide

      1. Load the page;
      2. The text field should show "Placeholder";
      3. Click on "BUTTON" first. A validation message should appear;
      4. Click on "LINK". A validation message is supposed to show, but it doesn't.

      Show
      1. Load the page; 2. The text field should show "Placeholder"; 3. Click on "BUTTON" first. A validation message should appear; 4. Click on "LINK". A validation message is supposed to show, but it doesn't.
    • Affects:
      Release Notes
    • Release Notes Docs Status:
      Documented as Known Issue
    • Release Notes Text:
      Hide
      When a JSF form is submitted using a h:commandLink, the onsubmit listener of the placeholder component is not triggered. This behaviour can interfere with the enforcement of component validations. The problem originates upstream in Mojarra and will be addressed in Red Hat JBoss Enterprise Application Platform 6.4. In the interim, a workaround for this issue is to use the a4j:commandLink instead of the h:commandLink.
      Show
      When a JSF form is submitted using a h:commandLink, the onsubmit listener of the placeholder component is not triggered. This behaviour can interfere with the enforcement of component validations. The problem originates upstream in Mojarra and will be addressed in Red Hat JBoss Enterprise Application Platform 6.4. In the interim, a workaround for this issue is to use the a4j:commandLink instead of the h:commandLink.

      Description

      When using <rich:placeholder> inside <rich:autocomplete required="true">, <h:commandLink> doesn't validate an empty field but <h:commandButton> does.

      Snippet from the attached reproducer:

      <h:form>
          <rich:autocomplete mode="client" autocompleteList="#{richBean.names}"
                             value="#{richBean.name}" required="true">
              <rich:placeholder value="Placeholder"/>
          </rich:autocomplete>
          <h:commandButton value="BUTTON"/>
          <h:commandLink value="LINK"/>
      </h:form>
      

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  bleathem Brian Leathem
                  Reporter:
                  iweiss Ingo Weiss
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  11 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: