JSF/Facelets: why is it not a good idea to mix JSF/Facelets with HTML tags?

Question

I've read this several times now: some developers aren't advocates of interleaving JSF/Facelets tags with HTML tags in their XHTML files. Obviously the HTML tags won't be part of the UI component tree, but what's the disadvantage of that?

I often find code examples where the authors do that kind of mixing:

http://www.ibm.com/developerworks/java/library/j-facelets/

http://www.packtpub.com/article/facelets-components-in-jsf-1.2

http://oreilly.com/catalog/9780596529246

"Seam in Action" also interleaves JSF/Facelets and HTML tags.

I'm confused about what to actually use. I started out mixing tags, but I'm beginning to believe it was probably not the right choice. However, I fail to see why the puristic approach is preferrable.

I know for certain that I have a table where the JSF datatable doesn't give me enough flexibility to display what I need to, so doing it puristically isn't possible.

Furthermore I'm wondering why none of the examples above use f:view etc. instead of the hardcoded html, head, body etc. tags.

Can anyone please clear this up for me?

OK this helps. At least regarding div and span, but how do I manage p, br, and especially headings? — Kawu
From my answer in the referenced question: "In practice I found it hard to follow this recommendation and ended up mixing html and jsf, e.g. for headings or line breaks I use html." — Matt Handy
I don't see why this isn't a good idea and that this is disappointing. Maybe you're victim of the myth that mixing JSF+HTML=bad which was caused during JSF 1.0/1.1 ages? For more history, see stackoverflow.com/questions/3273595/… — BalusC

BalusC BalusC · Accepted Answer · 2011-09-06T13:40:34

During the JSF 1.0/1.1 ages this was indeed "not a good idea", because all the HTML was not automatically taken in the JSF component tree when using JSP as view technology. All plain HTML was eagerly by JSP rendered before the JSF component tree. E.g.

<p>Lorem ipsum <h:outputText value="#{bean.value1}"> dolor sit amet<p>
<p>Consectetur adipiscing <h:inputText value="#{bean.value2}" /> elit</p>

got rendered as

<p>Lorem ipsum dolor sit amet<p>
<p>Consectetur adipiscing elit</p>

value1
<input type="text" value="value2" />

To fix this you would need to bring <f:verbatim> in.

<f:verbatim><p>Lorem ipsum </f:verbatim><h:outputText value="#{bean.value1}"><f:verbatim> dolor sit amet<p></f:verbatim>
<f:verbatim><p>Consectetur adipiscing </f:verbatim><h:inputText value="#{bean.value2}" /><f:verbatim> elit</p></f:verbatim>

This was a real maintenance pain. This was one of the major reasons why JSF 1.0/1.1 was so hated.

Since JSF 1.2, with the new view handler, the <f:verbatim> was not necessary anymore. Developers can now breathe relieved. Moreover, the new view handler allowed JSF to use a different view technology than JSP and this way Facelets was born.

JSF/Facelets: why is it not a good idea to mix JSF/Facelets with HTML tags?

2 Answers

See also: