Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 45394 invoked from network); 6 Apr 2007 15:53:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Apr 2007 15:53:14 -0000 Received: (qmail 30060 invoked by uid 500); 6 Apr 2007 15:53:17 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 29793 invoked by uid 500); 6 Apr 2007 15:53:16 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 29782 invoked by uid 99); 6 Apr 2007 15:53:16 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Apr 2007 08:53:16 -0700 X-ASF-Spam-Status: No, hits=3.2 required=10.0 tests=HTML_10_20,HTML_MESSAGE,MIME_BOUND_NEXTPART X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [216.148.227.151] (HELO rwcrmhc11.comcast.net) (216.148.227.151) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Apr 2007 08:53:07 -0700 Received: from rmailcenter80.comcast.net ([204.127.197.180]) by comcast.net (rwcrmhc11) with SMTP id <20070406155246m11005g8r0e>; Fri, 6 Apr 2007 15:52:46 +0000 Received: from [208.3.133.131] by rmailcenter80.comcast.net; Fri, 06 Apr 2007 15:52:46 +0000 From: gvanmatre@comcast.net (Gary VanMatre) To: "MyFaces Discussion" Subject: RE: Re: New to MyFaces Date: Fri, 06 Apr 2007 15:52:46 +0000 Message-Id: <040620071552.14327.46166CCE000250F9000037F722007601800A9D9B0E03020E9009@comcast.net> X-Mailer: AT&T Message Center Version 1 (Oct 4 2006) X-Authenticated-Sender: Z3Zhbm1hdHJlQGNvbWNhc3QubmV0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_14327_1175874766_0" X-Virus-Checked: Checked by ClamAV on apache.org --NextPart_Webmail_9m3u9jl4l_14327_1175874766_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit >From: "Iordanov, Borislav (GIC)" > > 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). > I disagree with this statement. I believe that it says just the opposite. It would have been very easy for the first draft of the JSF specification to be completely focused on a single templating solution (JSP). What I find interesting is that the focus was on building an API that was extensible and not targeted at a specific template technology. I don't think that JSP will go anywhere anytime soon. The JSF/JSP support is much better in JSF 1.2. However, hopefully the work done with Facelets and Shale Clay (see how I got a plug in there) will open the doors for more than one method of creating JSF view's. I'd like to see an option that completly insulates the developer from markup. A design mode that would be like the rich tools for creating fat GUI's with all kinds of reuse through composition options and visual form inheritance. At that point, the ability to plugin multiple render kits would be really handy. Gary > -----Original Message----- > From: news [mailto:news@sea.gmane.org] 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... > --NextPart_Webmail_9m3u9jl4l_14327_1175874766_0 Content-Type: text/html Content-Transfer-Encoding: 8bit
>From: "Iordanov, Borislav (GIC)" <boris@miamidade.gov>
>
> 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).
>
 
I disagree with this statement.  I believe that it says just the opposite.  It would have been very easy for the first draft of the JSF specification to be completely focused on a single templating solution (JSP).  What I find interesting is that the focus was on building an API that was extensible and not targeted at a specific template technology.
 
I don't think that JSP will go anywhere anytime soon.  The JSF/JSP support is much better in JSF 1.2.  However, hopefully the work done with Facelets and Shale Clay (see how I got a plug in there) will open the doors for more than one method of creating JSF view's.  I'd like to see an option that completly insulates the developer from markup.  A design mode that would be like the rich tools for creating fat GUI's with all kinds of reuse through composition options and visual form inheritance.  At that point, the ability to plugin multiple render kits would be really handy.
 
 
Gary
 
 

> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] 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...
>
--NextPart_Webmail_9m3u9jl4l_14327_1175874766_0--