Trying to understand immediate=”true” skipping inputs when it shouldn’t

by

With immediate="true" on the button, the action is indeed invoked during apply request values phase and all the remaining phases are skipped. That’s also the sole point of this attribute: process (decode, validate, update and invoke) the component immediately during apply request values phase.

All inputs which do not have immediate="true" are ignored anyway. Only inputs which do have immediate="true" are also processed, but this happens also during apply request values phase. Why should the remaining phases be invoked if everything has already taken place in the apply request values phase?

In the Debug JSF lifecycle article you can find the following summary which should enlighten when to (not) use the immediate"true":

Okay, when should I use the immediate attribute?

If it isn’t entirely clear yet, here’s a summary, complete with real world use examples when they may be beneficial:

  • If set in UIInput(s) only, the process validations phase will be taken place in apply request values phase instead. Use this to prioritize validation for the UIInput component(s) in question. When validation/conversion fails for any of them, the non-immediate components won’t be validated/converted.

  • If set in UICommand only, the apply request values phase until with update model values phases will be skipped for any of the UIInput component(s). Use this to skip the entire processing of the form. E.g. “Cancel” or “Back” button.

  • If set in both UIInput and UICommand components, the apply request values phase until with update model values phases will be skipped for any of the UIInput component(s) which does not have this attribute set. Use this to skip the processing of the entire form expect for certain fields (with immediate). E.g. “Password forgotten” button in a login form with a required but non-immediate password field.

See also:

More Related Contents:

  1. commandButton/commandLink/ajax action/listener method not invoked or input value not set/updated
  2. h:commandButton/h:commandLink does not work on first click, works only on second click
  3. p:commandbutton action doesn’t work inside p:dialog
  4. Execution order of events when pressing PrimeFaces p:commandButton
  5. How make commandButton not fully refresh page? How to use f:ajax?
  6. Open new window by POST using h:commandButton
  7. Why was “immediate” attribute added to the EditableValueHolders?
  8. p:commandButton vs. h:commandButton
  9. h:commandButton not working inside h:dataTable
  10. How to provide a file download from a JSF backing bean?
  11. JSF Controller, Service and DAO
  12. How to install and use CDI on Tomcat?
  13. How to use enum values in f:selectItem(s)
  14. Unicode input retrieved via PrimeFaces input components become corrupted
  15. Why are there different bean management annotations
  16. How to call a method with a parameter in JSF
  17. When using @EJB, does each managed bean get its own @EJB instance?
  18. How validate two password fields by ajax?
  19. How control access and rights in JSF?
  20. h:messages does not display messages when p:commandButton is pressed
  21. how to do autocomplete=”off” at form level in JSF
  22. JSF convertDateTime with timezone in datatable
  23. Calling Managed Bean Method From JavaScript [duplicate]
  24. Is it possible to disable f:event type=”preRenderView” listener on postback?
  25. Bookmarkability via View Parameters feature
  26. javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL does not work anymore since Java EE 7 / EL 3.0
  27. Are @ManagedBeans obsolete in JavaEE6 because of @Named in CDI/Weld?
  28. c:forEach inside primefaces(e.g. p:panelgrid) inside ui:repeat
  29. JSF 2 dataTable row index without dataModel
  30. Accessing properties file in a JSF application programmatically

Leave a Comment