Setting this param to Development enables better error messages, including in the client-side JavaScript, at the cost of some performance. While setting this param to Production will turn off some error messages, and emphasize performance. Source: JSF 2.0 Reminder: Project Stage
Set the GET query parameters as managed properties in faces-config.xml so that you don’t need to gather them manually: <managed-bean> <managed-bean-name>forward</managed-bean-name> <managed-bean-class>com.example.ForwardBean</managed-bean-class> <managed-bean-scope>request</managed-bean-scope> <managed-property> <property-name>action</property-name> <value>#{param.action}</value> </managed-property> <managed-property> <property-name>actionParam</property-name> <value>#{param.actionParam}</value> </managed-property> </managed-bean> This way the request forward.jsf?action=outcome1&actionParam=123 will let JSF set the action and actionParam parameters as action and actionParam properties of the ForwardBean. Create … Read more
This problem is in JSF 2 also recognized and explained in detail in the following answer: How can I populate a text field using PrimeFaces AJAX after validation errors occur? If you were using JSF 2, you could have used OmniFaces’ ResetInputAjaxActionListener or PrimeFaces’ <p:resetInput> or resetValues=”true” for this. To the point, you need to … Read more
All you need to do is basically indeed just adding an empty object to the datamodel behind the value attribute of h:dataTable. But the same empty row needs to be preserved in the subsequent request as well. If the backing bean is request scoped, then the datamodel get reloaded without the empty row. This all … Read more
I have seen in JSF 2 that it is possible to pass parameters to method calls. Is there anything equivalent in JSF 1.2? Passing parameters to method calls is not specific to JSF 2. It is specific to EL 2.2, which is in turn part of JSP 2.2 / Servlet 3.0 / Java EE 6. … Read more