This is not specific to JSF. This is specific to HTML. The HTML5 forms specification section 4.10.22.2 basically specifies that the first occuring <input type=”submit”> element in the “tree order” in same <form> as the current input element in the HTML DOM tree will be invoked on enter press. There are basically two workarounds: Use … Read more
URLs are not resolved based on the file structure in the server side. URLs are resolved based on the real public web addresses of the resources in question. It’s namely the webbrowser who has got to invoke them, not the webserver. There are several ways to soften the pain: JSF EL offers a shorthand to … Read more
You could do so. It’s technically possible. But it does (design)functionally not make any sense. You’re basically tight-coupling the model with the controller. Usually the JPA entity (model) is a property of a JSF managed bean (controller). This keeps the code DRY. You don’t want to duplicate the same properties over all place, let alone … Read more
You need to realize that the <p:graphicImage> actually renders a <img src> element with just an URL which is then later individually invoked by the webbrowser when it’s about to parse the obtained HTML markup and present the results. So, whatever you do in the getter method of <p:graphicImage> it must be designed that way … Read more
Which one is recommended? Go ahead with XML namespaces on xmlns.jcp.org domain. This was newly introduced since Java EE 7 in 2013 (which covers a.o. JSF 2.2, Servlet 3.1, CDI 1.1, etc). Do note that this not only affects Facelets files, but also XML configuration files such as faces-config.xml, web.xml, beans.xml, etc. The old XML … Read more
Look closer at the stack trace. Here’s the relevant part: … org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:189) com.sun.faces.facelets.el.ELText$ELTextVariable.toString(ELText.java:217) com.sun.faces.facelets.el.ELText$ELTextComposite.toString(ELText.java:157) com.sun.faces.facelets.compiler.CommentInstruction.write(CommentInstruction.java:77) … It’s thus evaluating EL in a comment block (recognizable by CommentInstruction). A comment block is considered as template text. Facelets evaluates by default also EL #{} in template text. It’s like as if you’re writing <p>#{screenShotBean.takeScreenshot}</p> without any JSF … Read more
If you’re using JSF 2.x with Facelets 2.x instead of JSP, then both are equally valid. Even more, Facelets implicitly wraps inline content in a component as represented by <h:outputText> (in other words, it will be escaped!). Only whenever you’d like to disable escaping using escape=”false”, or would like to assign id, style, onclick, etc … Read more
Keep the message in the flash scope. It’ll survive the redirect. context.addMessage(clientId, message); externalContext.getFlash().setKeepMessages(true); return “users.xhtml?faces-redirect=true”; Note that older Mojarra versions have some peculiar Flash scope related bugs: issue 1755 – Flash scoped messages lives longer than next request – fixed in 2.0.7 / 2.1.4 issue 2130 – Flash cookie enables data exploits – fixed … Read more
Your best bet is to bind the <h:selectBooleanCheckbox> value with a Map<Item, Boolean> property where Item represents the object behind the corresponding row. <h:dataTable value=”#{bean.items}” var=”item”> <h:column> <h:selectBooleanCheckbox value=”#{bean.checked[item]}” /> </h:column> … </h:dataTable> <h:commandButton value=”submit” action=”#{bean.submit}” /> public class Bean { private Map<Item, Boolean> checked = new HashMap<Item, Boolean>(); private List<Item> items; public void submit() … Read more
You should use it if you want to have access to the entire UIComponent instead of just only its value. For example, to access some methods which can’t be invoked/bound in the view. This is answered in the 1st question you found: JSF component binding – some confusion The 2nd question which you found, component … Read more