> > I was obligated to tyr JSF for real, so far I've been only reading and > > checking some demos. I've got in a project where I HAD to learn JSF, and It > > made me like Tapestry even more. JSF has such a Struts base that event that > > annoying mapping stuff is back but with a different name: navigation ... And > > the JSP looks like a salad of tags, petty.
If we go the "new" JSP2/JSF route, what do we really gain? It seems to be a cleaned up JSP+Struts, like Sun do EJB3 with POJOs now, was cribbed off Hibernate. Sun are trend followers, not trend setters. I can see the appeal for clients with a JSP base, but for new projects I'll push Tapestry every time now. There is Facelets, which creates a component like environment for JSF, but I can't imagine this being anywhere as good as Tapestry, and it's not mature. Problems with JSP are debugging it, and leaking of inapropriate code into it. I suppose the new EL will help tidy it up a bit, but really it's basically the same bad concept. It's good to hear this feedback anyway, thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
