How to let validation depend on the pressed button?

by

I understand that you want to filter based on the name input field. The <p:commandButton> sends by default an ajax request and has a process attribute wherein you can specify which components you’d like to process during the submit. In your particular case, you should then process only the name input field and the current button (so that its action will be invoked).

<p:commandButton process="@this name" ... />

The process attribute can take a space separated collection of (relative) client IDs of the components, wherein @this refers to the current component. It defaults in case of <p:commandButton> to @form (which covers all input fields of the current form and the pressed button), that’s why they were all been validated in your initial attempt. In the above example, all other input fields won’t be processed (and thus also not validated).

If you however intend to skip the required validation for all fields whenever the button in question is been pressed, so that you can eventually process multiple fields which doesn’t necessarily need to be all filled in, then you need to make the required="true" a conditional instead which checks if the button is been pressed or not. For example, let it evaluate true only when the save button has been pressed:

<p:inputText ... required="#{not empty param[save.clientId]}" />
...
<p:inputText ... required="#{not empty param[save.clientId]}" />
...
<p:commandButton binding="#{save}" value="Save" ... />

This way it won’t be validated as required="true" when a different button is pressed. The trick in the above example is that the name of the pressed button (which is essentially the client ID) is been sent as request parameter and that you could just check its presence in the request parameter map.

See also:

More Related Contents:

  1. Keep open when validation has failed
  2. JSF doesn’t support cross-field validation, is there a workaround?
  3. How to perform validation in JSF, how to create a custom validator in JSF
  4. Execution order of events when pressing PrimeFaces p:commandButton
  5. PrimeFaces validator not fired
  6. How to skip validation when a specific button is clicked?
  7. Change the default message “Validation Error: Value is required” to just “Value is required”
  8. How to display dialog only on complete of a successful form submit
  9. How to trigger args.validationFailed in PrimeFaces oncomplete
  10. Why does allow blank spaces?
  11. commandButton/commandLink/ajax action/listener method not invoked or input value not set/updated
  12. How to find out client ID of component for ajax update/render? Cannot find component with expression “foo” referenced from “bar”
  13. h:commandButton/h:commandLink does not work on first click, works only on second click
  14. Keep p:dialog open when a validation error occurs after submit
  15. Component to inject and interpret String with HTML code into JSF page
  16. Validation Error: Value is not valid
  17. p:commandbutton action doesn’t work inside p:dialog
  18. Can I update a JSF component from a JSF backing bean method?
  19. Is JSF validation client-side or server-side?
  20. How validate two password fields by ajax?
  21. JSF + PrimeFaces: `update` attribute does not update component
  22. PrimeFaces commandButton doesn’t navigate or update
  23. Using validator with a variable attribute in ui:repeat
  24. p:commandButton vs. h:commandButton
  25. c:forEach inside primefaces(e.g. p:panelgrid) inside ui:repeat
  26. List of events
  27. Defer loading and parsing of PrimeFaces JavaScript files
  28. Render multiple components with f:ajax
  29. Primefaces dialog + commandButton
  30. Conditionally provide either file download or show export validation error message

Leave a Comment