Iordanov, Borislav (GIC) ++ i have worked 6 months on jsf and given it up and wrote my html code direct into the servlet. the reason is: the whole control is under my hand, the rendered code is much simplier, works faster, consumes less space and is more flexible. we have spent one week for binding a table to a model and making it editable and ajax-able wihch took too much time. and when an exception occured, it was hard to detect the reason. one more thing which i disliked about about jsf was a big bug which was solved in newer versions but took much time for us and delayed the project. the reason was a simple synchronization problem where multiple threads accessed an object without synch.
On 4/6/07, Werner Punz <[EMAIL PROTECTED]> wrote:
Iordanov, Borislav (GIC) schrieb: > I'm not sure what "statistics" you are looking for. I haven't done an > industry analysis. But in general, JSF is heavyweight machinery without > any substantial benefit. Simple things are complicated and complicated > things impossible. It was obviously designed by (probably smart, Java > knowledgeable) people that have no serious experience with web > development. A well-known example is that it still doesn't work well > with JSP (a technology for which JSF was designed from the start!) and > it probably never will. > > JSF 1.2 does (myfaces soon will have jsf 1.2 level) and facelets basically do what jsp does. You basically speak about the mixin problems of html and jsf (verbatim tags) this problem is gone in the jsf 1.2 spec, and in facelets, facelets also eliminates problems introduced by jsp...
