Frequently Asked Questions

Q: How does Tapestry compare to other frameworks?

Tapestry is very much unlike most other frameworks in that it doesn't use code generation; instead it uses a true component object model based on JavaBeans properties and strong specifications. This gives Tapestry a huge amount of flexibility and enables dynamic runtime inspection of the application with the Tapestry Inspector (a mini-application that can be built into any Tapestry application).

Q: How is the performance of Tapestry?

My own testing, documented in the Sept. 2001 issue of the Java Report, agrees with other testing (documented in the Tapestry discussion forums): Using Tapestry involves a very modest, 5 - 15% performance penalty that is completely dwarfed by the costs of RMI and database access.

Q: What does it cost?

Tapestry is open source and free. It licensed under the LGPL, which allows it to be used even inside proprietary software.

Q: What is the relationship between Tapestry and Primix?

Primix was my (Howard Lewis Ship's) employer during the period that Tapestry was initially developed. I've since left Primix, but Tapestry continues to evolve and mature.

.....................................................

The Developer's Guide contains more specific, technical questions and answers.