Write a review to share your experiences with open source!
On DevRates we focus on reviews by developers using libraries on their daily work.
Interested in the latest trends and top-rated open source projects for all layers of your application?
DevRates contains projects reviews of most popular tagged categories and programming languages.
Follow projects and don't miss any news from blogs and twitter on your wall.
Your company is looking for talented developers? Register on DevRates and show your technology stack on your company profile.
Apache Tapestry is an open-source framework for creating dynamic, robust, highly scalable web applications in Java or other JVM languages. Tapestry complements and builds upon the standard Java Servlet API, and so it works in any servlet container or application server.
Tapestry is released under the Apache Software License 2.0.
Tapestry has a long history, with the oldest code dating back to January 2000. That means a lot of releases. At this time, Tapestry releases 3 and 4 are no longer being developed; developer effort for the past several years has focused on Tapestry 5.
full review »
I searched long and hard for a Java-based web framework and settled on Tapestry 5. I'd used Tapestry 4 before, but 5 is far, far better. It's amazingly easy to use and requires no icky XML configuration. Integration with Hibernate and my DAOs was very easy. Updates have been very easy as well, having gone from 5.0.x to 5.3.3 with minimal changes.
What I enjoy most is how little code and HTML is needed to make a useful database-driven page. It's embarassing little code, actailly. Documentation, like with most open source projects, could be better, but ti's much better than it was in the earlier days. Community support via the mailing list has always been excellent.
full review »
Having been active in the wonderfull world of Java web applications since 2001 I have tried and seen a fair few framworks. It has often been a painfull excersize shifting frameworks during the lifetime of your project due to shortcomings only found in a later development phase. The characteristics of being able to push out a quick prototype and customizing/extending a framework's behaviour to your custom needs have been mutually exclusive in almost all frameworks I have encountered. Not Tapestry 5! The share speed with which we can now deliver a prototype and simultaniously use the same framework to tweak our hight-performant clustered applications is great! Tapestries IoC service architecture allows you to pretty much take it anywhere you wish without forking the source. All with great defaults that work out of the box. That along with it's easy component architecture, strong and growing AJAX/client support, live class reloading (=no restarts while developing), unit and integration testing framework and its friendly and active community has made me a believer.
I have been introduced to Tapestry 5 in 2007 (sitll in Alpha back then) and have consistently chosen it as my framework of choice ever since. Feel free to contact me if you'd like to get some further feedback or have some questions answered.
full review »
As a long-time Tapestry user, I've seen things evolve considerably from 3->4 and especially 4->5. While these upgrades were painful, the application we get to work on today is vastly easier and more enjoyable to develop. New developers who join our team describe our tech stack as "cutting edge" and love the level of productivity they can achieve using this framework. Howard (the creator) actively works with multiple clients building large-scale Tapestry applications, and that real-world focus shows as the framework is constantly evolving to meet new challenges. Of course Tapestry has always been the gold-standard of error reporting. I can hardly imagine going back to a framework that doesn't give me line-precise error reports with every exception.
full review »
I have touched a lot of frameworks over the years, but none is truly simple in the way that Tapestry 5 is. Tapestry turns a lot of what web developers assume on its head. The abstractions are simple and powerful. However, many developers get upset when they can't create components dynamically (in a traditional sense) and get confused when they realize that they don't have to deal with get and post variables. But once you let go, you can't turn back. Life is better with Tapestry.