Tapestry 5 was... Wow. It was the effect it did to me and the other tester.
Its simplicity is amazing : its a joy to create new components (simple
POJOs with some conventions and annotation), test them and reuse
them along your application. The separation between HTML and logic is
rather good, the reload facility a must have (Wicket also have this), the
injection framework is amazing.
Tapestry
was a success for the project, but had two critical failings: 1. Backwards
compatibility 2. Documentation and project resources
Apache Tapestry 5 is even more productive than before. There's a good set of books, and a large community. Tapestry is productive. No need to stop and start your application. I like its template approach. It is not a component-based framework, so it is more close to Spring MVC and Play!
Tapestry - takes yet another approach for web development. It lets you sprinkle tapestry tags in your plain HTML, which provide the necessary logic/data. This is the second best I liked personally because I can work on HTML directly without resorting to JSPs, etc.
No comments:
Post a Comment