russelldb

Tapestry means a lot of things. Tapestry 4 is a different beast to Tapestry 5. Tapestry 4 is stable and mature and reasonably well used.

Tapestry 5 is fast changing, in beta and a tad unstable. Neither are strictly speaking enterprise ready.

The big question is why would you? When there is Spring MVC, Wicket, JBoss Seam why would you

A) Write a competing framework on your own?
B) Use such a framework?

I think as a framework it is OK. It has some nice ideas though the implementation leaves you jumping through hoops if you want non-default behaviour.

The Docs are poor. They cover a lit of ground conceptually but with very few examples. I get the impression they were written in a hurry by an engineer.

The community is small but pretty helpful as long as your question doesn't point up a deficiency in the Tapestry 5 design.

In general I would say IF you are looking for a framework to Proof Of Concept or prototype a Java Web App. then try Tapestry 5. The risks are just that it is unproven and there are few developers. Kudus to Howard Lewis Ship for seeing a gap where there is none and filling it with a framework that does a little less than the alternatives.

If you want fast dev and convention in Java use Groovy on Grails. If you want enterprise standards use Jboss Seam of Spring MVC. Or try this. It is intriguing and may well grow into a good 'un IF the project team let more people commit useful code.