p:commandButton in your case is (an has to be) non-AJAX button (you set this by adding ajax=”false” attribute). In that case update attribute and p:ajax tag doesn’t have any sense (as they are only for AJAX requests). When you have file download your application sends streaming of some type, and you see Save File dialog. … Read more
@Named gives a CDI managed bean an EL name to be used in view technologies like JSF or JSP. Note that in a CDI application you don’t need the @Named annotation to make a bean managed by CDI (thanks to @Karl for his comment). @ManagedBean makes the bean managed by JSF and you can: inject … Read more
Not specifically for required=”true”, but you can check by #{facesContext.validationFailed} if validation has failed in general. If you combine this with checking if the button in question is pressed by #{not empty param[buttonClientId]}, then you can put it together in the rendered attribute of the <h:outputScript> as follows: <h:commandButton id=”add_something_id” binding=”#{add}” value=”Add” action=”#{myBean.addSomething(false)}”> <f:ajax execute=”@form” … Read more
No, it is not possible to use variable arguments in EL method expressions, let alone EL functions. Your best bet is to create multiple different named methods with a different amount of fixed arguments. public static boolean isValueIn2(Integer value, Integer option1, Integer option2) {} public static boolean isValueIn3(Integer value, Integer option1, Integer option2, Integer option3) … Read more
To start, the view scope is bound to a particular page/view. Multiple views won’t share the same view scoped bean. The view scope starts with an initial GET request and stops when a POST action navigates with a non-null return value. There are in general the following scenarios, depending on whether the browser is instructed … Read more
This is not Mojarra specific. This is Tomcat specific (JBoss uses Tomcat as servletcontainer). Add the following VM argument to startup options. -Dorg.apache.el.parser.COERCE_TO_ZERO=false To my experience, this one should actually only apply on Number properties (int, long, etc), however since a certain late Tomcat 6.0.x version (at least after 6.0.20) it seems to be broken … Read more
It isn’t possible to define columns based on row data. Imagine that row 1 has 2 columns, row 2 has 6 columns, row 3 has 1 column, etc how would you ever produce a technically valid table in HTML? Each row must have the same amount of columns. You’ve 2 options, depending on whether can … Read more
JSF/Facelets uses by default UTF-8 to decode HTTP request parameters. GlassFish itself uses by default ISO-8859-1 do decode HTTP request parameters. HTTP request parameters can be parsed and decoded only once and this happens whenever a request parameter is requested by the code for the first time like so request.getParameter(“name”). So, if a request parameter … Read more
This is somewhat subjective, but ala, it boils down to the following: Navigation rules in XML are a maintenance hell. Using navigation rules suggests that the web application in question suffers from the “one URL behind” problem which causes bad user experience (pages are not bookmarkable). Using navigation rules suggests that the web application in … Read more
The value which is passed through the converter is not the option label as you seem to expect, but the option value. The best practice is to not do this in the model side, but in the view side, because the model shouldn’t need to be i18n aware. As to the approach, you’re basically unnecessarily … Read more