"Tapestry is an open source web application framework written in Java. Highly-interactive and content-rich applications can be easily developed using this framework."
"The majority of the work was the straightforward transformation of the JSP pages into Tapestry pages. In many ways, this was a purely mechanical effort, converting JSP tags and scriptlets (Java code embedded within a JSP) into proper Tapestry pages and templates. The 1.0 site included a large number of "components", in the form of JSP snippets that were included by top-level JSPs to form complete pages. Tracking down these individual files and replicating their behavior was a painstaking, but manageable, chore."
"A few months ago while I was at the NFJS conference in Denver Colorado I was talking with Erik Hatcher about why he liked Tapestry so much. While his story wasn?t convincing enough for me to drop everything and check it out, it was enough for me to closely watch the project. For those of you who haven?t heard or played with Tapestry here is a quick elevator explanation. Tapestry is one of the three Jakarta sponsored web frameworks, http://jakarta.apache.org/tapestry/. Unlike the other two, Tapestry is very component centric in its design. Tapestry is not a new framework, it has been around for a while and has recently gained a lot of popularity due to the abuse URL-based or command-driven frameworks have been getting and the general attention to a component-based approach to web development, since this model is similar to JSF. This will simply be a review of the book, Tapestry in Action, not the framework, which I hope to leave for another time. I hope you find it useful!"
"Another major feature of Tapestry is its use of HTML page templates. In Tapestry, each page is an HTML template containing browser-friendly HTML tags. Unlike JSP, JSTL, or JSF pages, creating Tapestry pages is relatively easy using common Web design tools, and you can preview them in a Web browser."
"Apache Tapestry is an open-source framework for creating dynamic, robust, highly scalable web applications in Java. Tapestry complements and builds upon the standard Java Servlet API, and so it works in any servlet container or application server."
"In this article, I've moved beyond the initial overview of Tapestry (from "In tune with Tapestry, Part 1") to show you how to actually develop applications with the Tapestry framework. Rather than focus on a lot of code, I decided to concentrate on the process of developing applications using Tapestry, and doing it well. While most Java programmers can easily learn a new API, many have a much harder time figuring out how best to use that API. One thing I hope you've picked up from this article is the importance of planning in Tapestry development, and how much well-made plans will contribute to your eventual execution. Another nice aspect of the Tapestry development process that I've highlighted is re-use. By carefully thinking through your components before you write them, you can end up with a reusable toolbox of components, rather than having to write lots of disparate applications that don't share components."
"Because Tapestry uses HiveMind to determine and download dependencies, your first step is to let Tapestry know where you've put the HiveMind files. Navigate into your Tapestry directory -- perhaps something like /usr/local/java/tapestry-4.0-beta-12 -- and then into the config directory. You should see a build.properties file. When you open it up, it will look something like what you see in Listing 1. Several of the core libraries and dependencies for Tapestry are listed here, along with their locations. This list doesn't reflect all of the dependencies needed by Tapestry, but it's the dependency set needed for compiling basic Tapestry applications."
"In a continuation of my series of articles about Java Web development frameworks, this article will look at the Tapestry framework. Because Tapestry is a rather large framework, one article is not enough to cover most of its features. I decided to split the discussion about Tapestry into two parts. In this first part, I will focus on the configuration of the framework in an enterprise-level IDE such as JBuilder 2005 and prepare the groundwork for a working example in the second part. I will also describe the structure of the framework and its main features in this article, and concentrate on more specific features and details in the second part."
"In the first part of this article, I discussed the main structure of the Tapestry framework, as well as its setup and configuration in an enterprise scale development environment such as JBuilder 2005. In this article, I will further explore the features of the framework and discuss specific components and pre-build modules. A sample application that uses Tapestry is included for your reference as well."