Jesse Alexander (KSFD 121) schrieb: > seems that mileage really varies > > We have heard from projects that they never would have made > it in time without JSF given their scarce resources. >
Actually I am one of this, my first JSF project was in 2005 afair it was a one man show, with about one month from spefication got in into delivery. Just to sum it up, with struts it would have taken at leat three times as long, with a pure servlet solution basically half a manyear. Tapestry and other component based frameworks like webobjects probably would have given me a similar creation time. The main problem of the app was, that it was intranet with a lot of specialized component stuff. Not doable anymore without a huge effort in action based environments, the ui was too close to a rich client ui. Anyway the speed of development was convincing enough for me to stay on the framework for future apps, and I have yet to regret it. > Thinking about the bad maintainability of System.out. webapps > I am HAPPY using JSF. Wouldn't want to go back to those old times. > > And using Facelets even the "component"-writing is really fun. > Actually the first thing which led to the introduction of jsps in the first place was that the pure servlet based approach basically resulted in unmaintainable apps, which was in 1997. Sorry to say that but the webframeworks (and also JSF) currently are catching up to webobjects which already had everthing in in 1996. Webobjects has stalled and is moving slowly into oblivion, while the other frameworks are slowly surpassing it.
