Welcome to Tapestry 5 Documentation root page.
An overview of Tapestry's general approach and philosophy
A quick guide to creating your first Tapestry project, using Maven
Picks up where Getting Started leaves off, explaining in greater detail how Tapestry works
A guide to common overrides and extensions to Tapestry
A quick place to check for common problems and solutions
Tapestry 5 Reference and API
Along with the reference documentation, we provide a set of concise guides to help you in your everyday work with Tapestry.
- Component Cheat Sheet is a concise guide to component classes, methods and annotations
- Refcard A color, six page foldout guide to Tapestry 5.0 (PDF)
detailed references to the concepts behind Tapestry and beyond.We provide a collection of
- Go to the main user guide's page to get access to the whole documentation stack
- Unit test your application with Tapestry test utilities
- Integrate Spring into your Tapestry application
- Use Tapestry Hibernate integration to build your data access layer
Published Articles on Tapestry
Tapestry Developer and Community Blogs
- Tapestry Central is Howard Lewis Ship's blog. As the creator of Tapestry, he provides a lot of valuable information on Tapestry's latest features and future directions.
- Igor Drobiazko's blog contains a lot of fresh news on Tapestry development and will guide you through the most exciting parts of Tapestry. Igor is a Tapestry Committer and PMC member.
- Andreas Andreou's blog (committer & PMC) has lots of news and entries on Tapestry 4 and 5.
- Spread the source's blog (Christophe Cordenier and Robin Komiwes committers's blog) has lots of news and advanced tutorials on Tapestry 5.
More blogs ...
The primary method of discussion is on the Tapestry users mailing list: email@example.com. You can subscribe by sending e-mail to firstname.lastname@example.org. This is the appropriate mailing list to learn more about Tapestry, to request help, and to socialize.
The second mailing list is email@example.com. You can subscribe to this list by sending e-mail to firstname.lastname@example.org (mailto: email@example.com). This list is used by the Tapestry PMC and committers to run votes, discuss issues and fixes, and plan the future of Tapestry. Please don't use this mailing list to ask for support.
Mailing list archives are available at http://tapestry.markmail.org/.
Reporting Problems / Getting Support
Tapestry issues are tracked in the Apache JIRA.
Unless your problem is clear as day, it's a good idea to discuss it on the Tapestry Users mailing list first, before adding an issue. At the same time, it's generally unlikely that a bug will be fixed unless a JIRA Issue is created.
Eric Raymond has a detailed guide to asking questions the right way. If you are not getting a response to your problem, it's likely because you aren't asking it the right way.
Just saying something is "broken" or "failed" is not enough. How did it fail? Did it do the wrong thing? Throw an exception? Not respond in any way? What exactly did you expect to happen? All of this information should be made available when looking for help, plus context on the general problem you were trying to solve in the first place (there may be a better solution entirely). Read Eric Raymond's guide ... it's fun and informative.
Source Code Access
Source code for Tapestry can be downloaded along with pre-compiled binaries.
Tapestry uses Subversion to manage the project's source code.
Web access to the Tapestry repository is available as http://svn.apache.org/viewvc/tapestry/tapestry5/trunk.
Access using Subversion client:
There's also some notes on using Git to access Tapestry.
There is an active flow of questions and answers about Tapestry at Stack Overflow.
Becoming a Contributor
The best way to become a contributor is to become active on the mailing list; Tapestry is known to have an active and helpful community on the mailing list, and the more mentors we can add, the better.
If you want to help out with documentation, you must sign an Apache Contributor License Agreement, at which point we can grant write access to the Confluence Wiki (where official documentation is created).
Providing patches (with tests!) is another way to become a contributor.
Becoming a Committer
Active contributors may be asked to become full committers, with write access to the source code. Generally, contributors who have been consistently active and helpful for three to six months are eligible for committer access. If you think you are in that category, don't be shy about contacting members of the Tapestry PMC (Project Management Committee).
Books on Tapestry
There are at least 8 published books on Tapestry, including two on Tapestry 5 — and more on the way.
- JavaServer Faces 2.0 vs. Tapestry 5: A Head-to-Head Comparison by Igor Drobiazko at Jazoon 2010
- Tapestry 5: Java power, Scripting Ease by Howard Lewis Ship at Devoxx 2009
- Community's Wiki (Moin Moin) contains a lot of user-generated information on different concrete web application use cases.
- Documentation Source wiki (Confluence) – the wiki used as the content editor for the official Tapestry documentation
The Developer Corner
Developer Information gives information needed by the Tapestry developers