You can get a request parameter id using the expression: <h:outputText value=”#{param[‘id’]}” /> param—An immutable Map of the request parameters for this request, keyed by parameter name. Only the first value for each parameter name is included. sessionScope—A Map of the session attributes for this request, keyed by attribute name. Section 5.3.1.2 of the JSF … Read more
FacesContext.addMessage(String, FacesMessage) requires the component’s clientId, not it’s id. If you’re wondering why, think about having a control as a child of a dataTable, stamping out different values with the same control for each row – it would be possible to have a different message printed for each row. The id is always the same; … Read more
and then I see that everything going through FacesServlet has .xhtml appended to it, so that the browser is requesting .png.xhtml files, .css.xhtml file – is this right? This only applies to resources included by <h:outputStylesheet> and <h:outputScript>. This is not related to the change in the URL mapping. This is related to the change … Read more
Yes, that’s definitely possible, assuming that you’re using JSF 2.0, part of Java EE 6. As to the managed beans and other JSF classes like validators, converters, etc, just annotate them with @ManagedBean, @FacesValidator, @FacesConverter, etc and package them in the JAR the usual way. You only need to provide a JSF 2.0 compatible /META-INF/faces-config.xml … Read more
You need to escape them to XML entities. <h:outputText value=”Tom & Jerry Show” /> This problem is not related to JSF per se, but to the view technology. You’re apparently using Facelets (which is perfectly fine!). Facelets is however a XML based view technology, so you would need to ensure that the template is well … Read more
Just declare an <error-page> in web.xml wherein you can specify the page which should be displayed on a certain Throwable (or any of its subclasses) or a HTTP status code. E.g. <error-page> <exception-type>java.lang.Exception</exception-type> <location>/error.jsp</location> </error-page> which will display the error page on any subclass of the java.lang.Exception, but thus not java.lang.Throwable or java.lang.Error. This way … Read more
Note that this is to be done differently in JSF 2.x Facelets, see this answer for detail. This is possible with a custom Facelets resource resolver. I would only not resolve them by HTTP, but just from the classpath. Just package the shared templates in for example the /META-INF/resources folder of the JAR file and … Read more
This works only with the in JSF 2.3 introduced javax.faces.annotation.ManagedProperty. @Inject @ManagedProperty(“#{param.id}”) private String id; The now deprecated javax.faces.bean.ManagedProperty annotation works only in JSF @ManagedBean classes. I.e. in instances which are managed by JSF. It does not work in instances which are managed by CDI @Named. Further, you’ve made another mistake: you’re trying to prepare … Read more
Facelets is a XML based view technology. XML has only five predefined entities. The is not among them. It works only when used in plain HTML or in legacy JSP (note: it doesn’t work in JSPX as that’s also XML based!). To fix this, you either need to declare the entity yourself in the … Read more
The DB-independent approach would be to let the User have a static Map<User, HttpSession> variable and implement HttpSessionBindingListener (and Object#equals() and Object#hashCode()). This way your webapp will still function after an unforeseen crash which may cause that the DB values don’t get updated (you can of course create a ServletContextListener which resets the DB on … Read more