What is "jsf"

Javaserver Faces (JSF) is a Model-View-Controller framework commonly used to create web applications. Using the standard components, rendering kit, HTML pages with status and can be defined using JSP or Facelets tags and linked to data model and application logic.

Information to provide when asking JSF questions

If you want accurate answers to your JSF questions, you’ll get better answers faster by including the following information in the question:

  • ** What implementation and JSF version you are using** Mojarra or Myfaces? 1.0.x , 1.1.x , 1.2.x , 2.0.x , 2.1.x ou 2.2.x? Particularly the difference between 1.x and 2.x is too big to be able to give a reliable answer, which can cover both versions. In addition, each of the JSF implementations may have its own specific set of bugs/tricks version so that the respondent can, if necessary, take into account.

  • What technology are you using view JSP or Facelets (XHTML)? If you have not mentioned in the question (for example, by code, tags, stacktrace, etc.) that you are using JSF 2.x, then Facelets are often assumed, since JSP is obsolete since JSF 2.0.

       Note that while Facelets uses by default the XHTML, XHTML extension nay is necessarily Facelets. So when asking a question specifically about Facelets, please do not use the term "XHTML" and certainly do not use [xhtml] tag. Those who know about XHTML don’t necessarily know something about Facelets.

  • Any face messages or warnings/errors/exceptions in server logs If the app seems to be crashing silently, make sure you’ve added a tag in his view to prevent this. You lose all the faces messages, also make sure that you have read the server logs from top to bottom. Provide this information in the question.

  • Provide the smallest possible copy and Paste example and rotatable, but complete! (SSCCE) Import declarations and getters/setters are, however, not strictly necessary, as a sane bit IDE can only autocomplete/generate them, also nothing out <h:body> in view is not strictly necessary, since usually also speaks for itself.

Easier would be to copy the problematic code in a new project and remove step by step as much as possible irrelevant resources (CSS/JS/images), labels (templates, layout, text, etc), attributes (style, styleClass , title, etc) and Java code (independent properties, Ejbs, etc ), provided the problem is still exposed.