The point of jsp tag handlers and tld files is that it is a linguistic facility, similar to functions, classes etc in programming languages, that allows one to create abstractions, or coherent sets of such in order to encapsulate and express concisely common tasks in different contexts. I'm curious, what's the equivalent in facelets and why is it better than JSP tags (this is just me trying to avoid reading facelets docs)?
I haven't wasted a lot of time developing JSP tags. JSP tags are the greatest invention in the whole Java web server programming world. And the declarative XML-ish syntax isn't so bad either. The parallel with Struts is not appropriate, in my opinion. Struts is a monument of vulgarity. -----Original Message----- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Friday, April 06, 2007 11:23 AM To: MyFaces Discussion Subject: Re: Re: New to MyFaces The statement that you want to continue to use JSPs, and yet complain that JSF is "heavyweight machinery without any substantial benefit" seems contradictory to me. In my opinion, backed up by two-years of JSF experience, the biggest flaw of JSF was attempting to use JSPs and all the unnecessary complexity that they bring. What point does it serve to write jsp tag handlers and jsp tld files? Facelets proves that they add no value since you can do the same tasks without them. Why use difficult-to-debug pages-compiled-as-java-code jsp processors when Facelets shows you can get the same functionality and better performance without it? No, facelets is not backwards compatible to JSP, although you can mix JSP and Facelets pages in the same application. And good riddance! Facelets isn't backward compatible to System.out.println() statements either :-) I'm sorry you wasted a lot of time developing jsp tags. I wasted a lot of time developing struts actions, but I'm not all that sad to see them gone. I know that there are those who are working on allowing JSP-compatiblity tags in facelets. Seems like a step backwards to me, but even that will likely happen at some point. JSF is component-based development. It's nice to see that the Java world is finally catching up to what WebObjects provided more than 11 years ago. I hope it doesn't take another 11 to catch up to where WebObjects is now (especially considering that WebObjects hast stagnated the last 5 years, as near as I can tell). My job is to provide solutions to problems, not constantly reinvent the wheel every time I need to display some kind of output. I'm still waiting for the time when I can design a component, drop it in a palette, then drag it out and configure it on my page in a WYSIWYG manner. JSF hasn't reached that point yet, but it's at least a possibility. And facelets allows me to create composite components in less than a minute. On 4/6/07, Iordanov, Borislav (GIC) <[EMAIL PROTECTED]> wrote: > I think the existence of facelets, the motivation behind it, show JSF's > failure to deliver on its promise (after so many years!). I haven't > looked into Facelets, not that I'm afraid to learn some new "view > technology". I just don't want to impose this "bug fix" to people that > have already invested time in learning and using JSP pages, with custom > tag libraries developed etc (is Facelets backwards compatible with JSP? > probably not). > > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz > Sent: Friday, April 06, 2007 4:36 AM > To: users@myfaces.apache.org > Subject: Re: New to MyFaces > > 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... > >
