There's a standard way of developing Facelets applications, with the .xhtml file extension, and using the <f:view> tag to specify the xml namespaces etc. Our timezone tutorial steps 6 and 7 adhere to that.

But, most IDEs don't support Facelets, so our users have to use tricks to take advantage of the JSPX support that gives them autocompletion etc, by making the Facelets files look like JSPX files, and using the jsfc attribute to make the <jsp:root> tag look like an <f:view> tag.

So, first off, we should document those techniques, in the Knowledge Base, and maybe in the PDFs that we ship with the downloads.

Secondly, we should look at our existing JSP sample code for timezone1-5 and component-showcase, and others, to make them do the JSPX IDE autocompletion stuff.

Thirdly, we should decide which samples should show the hybrid JSPX/Facelets approach, and which should use the pure Facelets approach. I think that component-showcase should definitely use the hybrid approach. It's kind of debatable about timezone 6, because it shows how to change the configuration from JSP to Facelets, so if we're making it hybrid, then it won't clearly demonstrate all of the changes.

Timezone 5 and 6 were sort of made specifically to show that the .jspx or .xhtml file could be the same, so maybe some documentation could highlight certain ways of JSPX and Facelets development that work for both, and certain things that are totally different.