JavaServer Faces and Tapestry

[Jeevan Bihari <je...@yahoo.com>]

  Has anyone compared Tapestry against JavaServer Faces ? If so, it would be great if they could
share their findings with the group.

Thanks,
Jeevan

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com

Re: JavaServer Faces and Tapestry

["Andrew C. Oliver" <ac...@apache.org>]

If you look back in the general @ jakarta archive, a few months ago 
there were plenty of reactions to JSF... 

In short....yuck.

-Andy

Jeevan Bihari wrote:

>  Has anyone compared Tapestry against JavaServer Faces ? If so, it would be great if they could
>share their findings with the group.
>
>Thanks,
>Jeevan
>
>__________________________________________________
>Do you Yahoo!?
>Yahoo! Web Hosting - establish your business online
>http://webhosting.yahoo.com
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>  
>

RE: JavaServer Faces and Tapestry

["Howard M. Lewis Ship" <hl...@attbi.com>]

JSF bad.  Tapestry good.

There's a couple of good rants by yours truly on
http://www.theserverside.com and http://www.javalobby.com.

JSF requires an outrageous amount of effort to accomplish simple things.

JSF has not demonstrated that it can scale in terms of complexity the way
Tapestry can.

JSF has not demonstrated that it is capable of creating true components.  I
trump up the Palette and the DatePicker, which both have sophisticated
client-side aspects that are still handled a seemlessly as a simple text
field.  Drop it onto the page and go.

JSF still expects you to do a whole lot of mechanical operations.  For
examples, it has form tags and form input tags (just like Tapestry has Form
and TextField), but it doesn't automatically know which input tags are
enclosed by the form; it relies on the developer to apply a particular kind
of naming pattern that identifies containment to the framework.

JSF still uses a page-oriented, not component-oriented, dispatch structure
reminicent of Struts.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry



> -----Original Message-----
> From: Jeevan Bihari [mailto:jeevanbihari@yahoo.com] 
> Sent: Tuesday, March 11, 2003 4:39 PM
> To: tapestry-user@jakarta.apache.org
> Subject: JavaServer Faces and Tapestry
> 
> 
>   Has anyone compared Tapestry against JavaServer Faces ? If 
> so, it would be great if they could share their findings with 
> the group.
> 
> Thanks,
> Jeevan
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Web Hosting - establish your business online 
http://webhosting.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org