You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by di...@multitask.com.au on 2003/06/02 01:31:11 UTC
Re: Tapestry Vs. JSF vs. Strusts vs. ...
Cool.
I have to take another serious look @ Tapestry for our paid work. I think
I need to get my toes wet checking out the tutorial and samples.....
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
"Howard M. Lewis Ship" <hl...@attbi.com> wrote on 30/05/2003 09:29:21 PM:
> It's all about where you want to focus your energies.
>
> With Struts and (what I understand of JSF), you spend way too much
> time doing plumbing. Tapestry
> does all the ugly plumbing; you don't have to be concerned with the
> servlet API: HttpSession,
> HttpServlet, HttpServletRequest ... all that stuff disappeers. You
> write just the tiny amount of
> code to be executed when "stuff happens" (link clicked or form
> submitted) in the form of a listener
> method. Tapestry does all the rest.
>
> Tapestry lets you code in the familiar world of stateFUL JavaBeans,
> rather than in the artificially
> stateLESS world of servlets.
>
> Tapestry has phenominal exception reporting; if there's an error in
> your HTML templates or your
> specifications (the companion files that provide Tapestry with the
> details of your pages) you get
> not just a stack trace, but the exact file and line where the error
> took place, along with a rundown
> of all the Servlet API objects (request, session, etc.). All the
> runtime objects (pages,
> components, bindings, whatever) are "tagged" with the location (file,
> line and column) from which
> they were generated.
>
> Tapestry doesn't use JSP ... Tapestry HTML templates are still valid
> HTML. JSPs (and even Velocity)
> instruments HTML by injecting a whole second language into the
> template: you template is a mix of
> HTML, XML, JSP directives and Java (for JSP) and HTML and Velocity
> directives (for Velocity). In
> Tapestry, your HTML is still HTML ... though in some cases, there are
> extra attributes on tags, and
> special interpretations of attribute values.
>
> Anyway, I've been encouraging the community to be a bit more vocal
> about why they feel Tapestry is
> so good. The 3.0 stuff especially gives you vast power and tremendous
> simplicity (and enough rope
> to hang yourself, but that's another discussion!). A 3.0 beta will be
> out, probably this weekend.
>
> --
> Howard M. Lewis Ship
> Creator, Tapestry: Java Web Components
> http://jakarta.apache.org/tapestry
>
>
>
> > -----Original Message-----
> > From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> > Sent: Thursday, May 29, 2003 9:37 PM
> > To: Tapestry users
> > Subject: Re: Congrats!
> >
> >
> > Howard,
> >
> > are there any good docs on why you would go Tapestry vs
> > JSF/Struts/etc??
> > --
> > dIon Gillard, Multitask Consulting
> > Blog: http://www.freeroller.net/page/dion/Weblog
> > Work: http://www.multitask.com.au
> >
> >
> > hlship@attbi.com wrote on 30/05/2003 02:17:25 AM:
> >
> > > Yes, it is very good to see this, we still need to get mindshare.
> > >
> > > However, what Tapestry really needs is more support from
> > the trenches.
> > > Shortly, there will be announcements on ServerSide and
> > JavaLobby. More
> > people
> > > need to read well worded endorsments and success stories. Posting
> > > here
> > is
> > > preaching to the converted.
> > >
> > > I think every person who reads this list has a vested
> > interest in the
> > success
> > > of Tapestry ... after all, who wants to go back to sevlets,
> > Struts and
> > JSPs?
> > > Therefore, it is incumbant on every person here to support
> > Tapestry a
> > > publically as possible.
> > >
> > > You should consider it your payment for the tens of
> > thousands of hours
> > the
> > > Tapestry team has invested in Tapestry. We can solve every
> > technical
> > challenge
> > > in the world and its all meaningless unless we wrest mindshare away
> > > from
> > JSF
> > > and Struts and the like.
> > >
> > > Tapestry can still fail, still be an "also ran", still be
> > beta to the
> > > JSF/Struts VHS. (Personally, I think of Tapestry as more
> > of a DVD/RW in
> > that
> > > analogy). Regardless, EVERY SINGLE TAPESTRY USER should
> > take time on
> > EVERY
> > > TAPESTRY ANNOUNCEMENT to voice their support. We must be loud. We
> > > must
> > even
> > > be obnoxious at times.
> > >
> > > Every time you see a Tapestry announcement on JavaLobby or
> > > TheServerSide
> > or
> > > elsewhere and you don't spent *one minute* to post a supporting
> > > message,
> > you
> > > are saying that you would rather slave away using JSF or some other
> > > ugly
> >
> > > framework. Period.
> > >
> > >
> > > --
> > > hlship@attbi.com
> > >
> > > Creator, Tapestry: Java Web Components
> > > http://jakarta.apache.org/tapestry
> > > > Glad to see that Tapestry is finally an official Apache
> > subproject!
> > > > It's about time that Tapestry had a stamp of approval you
> > can show to
> > > > managers!
> > > >
> > > > --
> > > > Bill Burdick <bi...@appliedreasoning.com>
> > > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> > tapestry-user-help@jakarta.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>