Actually, it's not really effective JSF if you are even using non-JSF tags.
JSF is intended to be a semantic framework with a decoupled rendering mechanism. In practical terms, that means things like being (potentially) to use the same application code on both standard HTML and WAP page-based systems, to be able to render raw graphics without any the need for HTML at all, and to be able to render items in a mixed mode such as HTML/JavaScript (AJAX).
If you go around dropping chunks of HTML in the abstract page definition, you defeat that intention. It may not bite you today, and it probably won't even bite you to morrow. But there may come a time when you'll wish you hadn't.
Customer surveys are for companies who didn't pay proper attention to begin with.
Bart Kummel
author
Ranch Hand
Joined: Nov 30, 2007
Posts: 81
posted
0
You should learn Facelets! It is fairly simple to use, in fact easier to use than JSP. I agree with Tim that ideally you should not have any (X)HTML code in your JSF page definition. But I know it may be a good pragmatic solution sometimes. A good compromise may be to use Facelets templates. You can keep the actual page definitions strictly abstract JSF page definitions then and only add some (X)HTML to your Facelets template(s).