In a recent blog post, Java EE 6 (JSR 316) specification co-lead Roberto Chinnici discussed the two leading proposals for the web profile in the upcoming Java EE 6 specification (For more information about profiles, one can start with this article on TheServerSide.) The part that caught me by surprise and confuses me greatly is why the inclusion of JavaServer Faces in the web profile would be controversial. Having spoken with an expert group member, who I will not out :), the argument comes down to this: “We shouldn’t force a broken technology, that is not the clear winner on people.” I think that’s a very interesting statement, in that it precludes doing just about anything in the spec. (more…)

Popularity: 74% [?]

At the lunch session of the OKC JUG today, a question was asked about the difference between the valueChangeListener attribute and <f:valueChangeListener/>. That is,

<h:selectOneMenu id="optionMenu" value="#{optionBean.selectedOption}" valueChangeListener="#{optionBean.optionChanged}" onchange="submit()"> <f:selectItems value="#{optionBean.optionList}" /> </h:selectOneMenu>

and

<h:selectOneMenu id="optionMenu" value="#{optionBean.selectedOption}" onchange="submit()"> <f:selectItems value="#{optionBean.optionList}" /> <f:valueChangeListener type="com.mycompany.MyValueChangeListenerImpl" /> </h:selectOneMenu>

The question was, which is “better?” There was also a question if the latter form automatically handled the JS on the parent component. I will now attempt to answer those questions now.
(more…)

Popularity: 81% [?]