“Trying to combine JSF and JSP is like trying to shoehorn a foot into a glove: it’s possible, but it’s really just a stopgap measure until something better comes along. In this article, JSF enthusiast Rick Hightower introduces you to what he likes best about Facelets: easy HTML-style templating and reusable composition components.”
After using SiteMesh, we found the need for a JSF templating solution. After a little research, we found Facelets. It is amazing at how it can simplify your development. If you are using JSF, you might want to give Facelets a shot.
-G
Doesn’t the need of facelet imply that JSF itself is incomplete and cannot be used directly?
The standard is supposed to make things vendor-independent, yet it itself is unable to cover the basic requirements so that all vendors will have to put various extensions to make it useful. Hasn’t anyone ever wondered how ridiculous this is?
Sorry, but JSF is just a joke. I used it for about a year and then I decided to try a couple of other things: namely Tapestry for J2EE and Rails for smaller side projects.
They completely missed the boat with JSF.
The RI of JSF from Sun is a joke, but utilizing MyFaces and Facelets is no joke. It is a very powerful and extensible application framework.
-G
JSF is definitely not a joke. I am using JSF toogether with Struts in my current project and they work together very well. The majority part of our project is to do scientific data query and the extended data table and page scroller provided in tomahawk make it very easy to generate data report.
Actually MyFaces currently is getting a huge component boost, in 1.1.2 there will be around 10-15 additional sandbox components (some of them will make it into tomahawk by 1.1.3), as we speak the tobago components
are coming out of the sandbox and will be another myfaces subproject and oracle just donated 113 components, parts of the adf faces to the opensource community and they are under incubation.
So myfaces in the long run will be several hundred components for web development. Which is a serious number to cover most if not all common cases.
So everyone dismissing JSF really did not get the point that this technology lives with components, and they are here already.
JSF has lots of community support, as it got into the market at just the right time (before the AJAX rush). People like http://www.icesoft.com and the already mentioned MyFaces have lots of good third party components.
Browser: Links (0.99; Linux 2.6.9-1.667smp i686; 121×53)
Still seems too much like pounding that old stone tablet of mixing content with presentation, prefer servlets, XML and XSLT.
Xml with xslt you have to try Cocoon, but I do not see really a point, xml+xslt has its own purposes, JSF is something entirely different it is a framework to build highly interactive server rendered applications, and facelets is a templating technology for enabling easy componentization.
XSl+XSLT is comparable to JSF like PDF to QT or the Win32 api, both try to fill different nieches of the presentation layer.