JavaServer Faces 2.2 and HTML5 support, why is XHTML still being used

by

It seems that you misunderstood the purpose of XHTML like as many people during the XHTML overhype a couple of years ago. Long story short: check our XHTML wiki page. Carefully read it. In a nutshell, Facelets absolutely doesn’t care about the doctype being used in the generated HTML output. You can perfectly fine declare a HTML5 doctype in a Facelets template.

It’s indeed unfortunate that Netbeans by default prepares the document with XHTML doctype while HTML5 is these days the recommended doctype. I don’t do Netbeans, but in Eclipse you can easily edit those templates and even create your own. You can just replace the whole XHTML doctype by a HTML5 one. You can find/create those templates via Web » HTML Files » Editor » Templates in IDE prefs.

Please note that the HTML5 support in JSF 2.2 has got nothing to do with being able to support specifically the HTML5 doctype. On the contrary, this is supported on all JSF versions, even when legacy JSP is being used. JSP and Facelets are view technologies which allows you to generate HTML output, which can perfectly fine be HTML5 as good. This is also elaborated in the following closely related answer: Is it possible to use JSF+Facelets with HTML 4/5?

Instead, the HTML5 support in JSF 2.2 covers the possibility to define custom JSF component attributes and turning custom HTML elements into JSF components. This was not possible in JSF 2.1 and before. Any custom JSF component attributes (including the HTML5-recommended data-xxx attributes) were simply ignored by the default JSF renderers. See also the following related answer: Custom HTML tag attributes are not rendered by JSF. In JSF 2.2 you can easily specify custom attributes by the new http://xmlns.jcp.org/jsf/passthrough namespace as follows:

<html ... xmlns:a="http://xmlns.jcp.org/jsf/passthrough">
...
<h:inputText ... a:autocorrect="off" />

This will end up in the by <h:inputText> unsupported attribute autocorrect to actually be included in the generated HTML output. Note that I use a XML namespace prefix of a (“attribute”) instead of p as shown in the Java EE tutorial, as it would otherwise clash with default XML namespace prefix p of PrimeFaces.

Turning custom HTML elements (including HTML5 elements) into JSF components is a matter of specifying a jsf attribute such as jsf:id.

<html ... xmlns:jsf="http://xmlns.jcp.org/jsf">
...
<header jsf:id="header">...</header>
<main jsf:id="main">...</main>
<footer jsf:id="footer">...</footer>

Those will under the covers be turned into UIPanel (like as <h:panelGroup>). And yes, they are referencable in e.g. <f:ajax render>.

In other words, “HTML5 support” is just again another buzzword for “Custom attribute support”.

More Related Contents:

  1. Is it possible to use JSF+Facelets with HTML 4/5?
  2. Redirect from an HTML page
  3. Why can’t the tag contain a tag inside it?
  4. How do I properly escape quotes inside HTML attributes?
  5. A Space between Inline-Block List Items [duplicate]
  6. Margin-Top push outer div down
  7. display: inline-block extra margin [duplicate]
  8. What is DOCTYPE?
  9. Custom HTML tag attributes are not rendered by JSF
  10. Error parsing XHTML: The content of elements must consist of well-formed character data or markup
  11. Add centered text to the middle of a horizontal rule [duplicate]
  12. The entity name must immediately follow the ‘&’ in the entity reference
  13. HTML: Is it possible to have a FORM tag in each TABLE ROW in a XHTML valid way?
  14. Making the main scrollbar always visible
  15. So what if custom HTML attributes aren’t valid XHTML?
  16. Best Way to View Generated Source of Webpage?
  17. Tick symbol in HTML/XHTML
  18. Valid content-type for XML, HTML and XHTML documents
  19. Change checkbox check image to custom image
  20. How to insert special characters like & and < into JSF components' value attribute?
  21. display:inline with margin, padding, width, height
  22. Conditional rendering of non-JSF components (plain vanilla HTML and template text)
  23. How to use an tag inside a in the middle of a text? [duplicate]
  24. Safari anchors on links not working
  25. Padding the top and the bottom of inline element
  26. HTML list-style-type dash
  27. How to fix favicon.ico error: “Failed to load resource: net::ERR_EMPTY_RESPONSE”
  28. Is div inside list allowed? [duplicate]
  29. What’s the point of valid CSS/HTML?
  30. JSF vs HTML(JSP) for enterprise portals UI layer. Which one to Choose? and WHY? [closed]

Leave a Comment