Post a Comment
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?
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.
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.



