Whilst your initial solution works, it’s in fact inefficient. This approach basically requires the entire object graph of the Country and State tables (even with circular references) to be fully loaded in Java’s memory per JSF view or session even though when you simultaneously use only e.g. 5 of 150 countries (and thus theoretically 5 … Read more
Just check the dropdown menu’s value in the rendered attribute of the target components and update their common parent by a <f:ajax>. Here’s a kickoff example: <h:selectOneMenu value=”#{bean.item}”> <f:selectItem itemValue=”one” /> <f:selectItem itemValue=”two” /> <f:selectItem itemValue=”three” /> <f:ajax render=”results” /> </h:selectOneMenu> <h:panelGroup id=”results”> <h:panelGroup rendered=”#{bean.item eq ‘one’}”> You have selected “one”. </h:panelGroup> <h:panelGroup rendered=”#{bean.item eq … Read more
It uses Object#equals() for that. You can change (fix) this behavior by implementing it accordingly on your entity. private Long id; @Override public boolean equals(Object other) { return (other != null && getClass() == other.getClass() && id != null) ? id.equals(getClass().cast(other).id) : (other == this); } Don’t forget the hashCode() to satisfy the equals-hashCode contract. … Read more
You can’t. That’s just how HTML works. You know, JSF is a HTML code generator. The JSF <h:selectOneMenu> generates a HTML <select><option> . The HTML <select> element will only send the value attribute of the selected <option> element. It will not send its label. But that shouldn’t be a big issue. You namely already know … Read more
Would it be possible to replace JSF Components by their plain HTML counterparts using JSFC and do something like this Nope. Ultimately, such a HTML element with jsfc attribute will be turned into a true JSF component in the JSF component tree and only the attributes supported by the component in question would be parsed … Read more
When the select item value is null, then JSF won’t render <option value>, but only <option>. As consequence, browsers will submit the option’s label instead. This is clearly specified in HTML specification (emphasis mine): value = cdata [CS] This attribute specifies the initial value of the control. If this attribute is not set, the initial … Read more
You can use <f:ajax> for this. When nested in an input component such as <h:selectOneMenu>, then it will by default be invoked when the input value is changed. You can specify a listener method which could prepopulate the data for the next component based on the current input value, and you can specify the client … Read more
Put the bean in the view scope and get rid of any business logic in getter methods. The bean must be placed in the view scope so that all previous selections and new available items are remembered for subsequent postbacks, otherwise things will fail when JSF needs to validate the selected item against the list … Read more
JSF has a builtin converter for enum, so this should do: @Named @ApplicationScoped public class Data { public Status[] getStatuses() { return Status.values(); } } with <h:selectOneMenu value=”#{bean.question.status}” > <f:selectItems value=”#{data.statuses}” /> </h:selectOneMenu> (note: since JSF 2.0 there’s no need anymore to provide a SelectItem[] or List<SelectItem>, a T[] and List<T> are accepted as well … Read more
Validation fails with the message “form:location: Validation Error: Value is not valid” This error boils down to that the selected item does not match any of the available select item values specified by any nested <f:selectItem(s)> tag during processing of the form submit request. As part of safeguard against tampered/hacked requests, JSF will reiterate over … Read more