After 18 months of developing with Tapestry 3.03, I don't know what my next 
framework will be, but you can bet it will be Tapestry.  Having worked with 
Model 1 Frameworks using JSP's and then working with Struts 1.x, I have had 
envough of anything related to .jsp or taglibs.  I have no experience with JSF 
or Wicket, but I do have 150 pages in Tapestry.  I have multiple libraries of 
components and even some custom components.  And when the time to upgrade comes 
along, it will probably be 5.x.

We have started three new products since mine and all of them have been 
Tapestry.

regards,

Mark

Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity



-----Original Message-----
From: Emmanuel Sowah [mailto:[EMAIL PROTECTED]
Sent: Wed 12/20/2006 2:13 AM
To: users@tapestry.apache.org
Subject: Can you comment on this?
 
Hi Guys,

I came across this article
http://www.infoq.com/news/2006/12/wicket-vs-springmvc-and-jsf and thought
probably someone here could comment. Is Tapestry really losing the battle
against Wicket?

Emmanuel

Reply via email to