>>The developers generally much prefer it, it is more productive, easier to
>>debug
>> and maintain ONCE the learning curve is done with.
I would like to say that Tapestry's learning curve is
less steep than JSF one.
John Coleman <[EMAIL PROTECTED]> wrote: I've team led and developed numerous
Struts apps over the years, some small,
some large. IMO unless the app is trivial form processing, Struts soon runs
into problems. Struts should be regarded as a low level framework upon which
to build your own app framework. The main problem with Struts is you usually
use JSPs, and they in themselves are difficult to manage. Most the larger
Struts apps I have worked on soon find that Struts hinders development and
restricts flexibility.
Architects have been critical of Struts
http://today.java.net/pub/a/today/2003/12/11/mvc.html?page=2 and I think
they are correct.
We have done just one app with Tapestry. The developers generally much
prefer it, it is more productive, easier to debug and maintain ONCE the
learning curve is done with.
Struts vs Tapestry is comparing apples and oranges really. You need to find
a framework that fits your business requirement.
John
----- Original Message -----
From: "Jonnalagadda, Sumithra"
To:
Sent: Wednesday, April 26, 2006 3:08 AM
Subject: tapastry vs struts
> We are currently evaluating different frameworks to build our e-commerce
> site.
>
> Struts
>
> Pros : huge user base and hence good support
>
>
>
> Cons : its stagnant.
>
>
>
>
>
> Tapestry :
>
>
>
> Pro : component based development
>
>
>
> Cons : not as big user base as struts.
>
>
>
> These are the preliminary points I could gather till.
>
>
>
> More experienced ones can you please help me make the right decision by
> sharing your experinces.
>
>
>
> Thanks
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
