Release Roundup

Apache Tapestry gets sewn up in 5.3 update

Chris Mayer

Sapphire 0.4 released too!

After a year of grafting, the Tapestry team were proud to announce the latest patching up of their Apache open source framework.

Howard Ship revealed that Apache Tapestry 5.3 contains 270 bug fixes, improvements and other minor changes, profiled in much further detail in the release notes. But here’s the highlight reel:

  • Improved performance: very large sites will see a 30 – 40% improvement in throughput
  • Decreased memory footprint: about a 30% decrease in memory utilization over 5.2
  • New components and services to support user alerts and notifications
  • Improved a simplified support for partial page rendering inside Ajax requests
  • Automatic JavaScript and CSS minimization (via YUICompressor)
  • Component reference details integrated into JavaDoc
  • Improved Maven quickstart archetype
  • Skinning and themeing support
  • Improved client-side presentation of server-side exceptions during Ajax requests
  • New components, including Ajax-enabled Tree, and Kaptcha
  • HTML5 Doctype support
  • Support for JSR-330 injection annotations

Top level project, Apache Tapestry is an open-source component-oriented Java web application framework to implement applications in accordance with the model-view-controller architectural pattern. Tapestry is primarily available for download via Maven, from the Maven central repository:


 You can also download the source or JavaDocs archives.




Konstantin Komissarchik was proud to announce the latest version of Sapphire 0.4, promising glistening new major enhancements.

Sapphire is a user interface development framework that improves productivity. Instead of focusing on individual widgets, layouts and data binding, the developers focus on modeling the semantics of the data and declaring the general intent of how the data it to be presented.

XML Binding and new APIs are on show for the update. The Sapphire Expression Language has been extended and will be flexible to use. Also appearing is the new annotation XmlDocumentType in DTD documents to determine the systemId or the publicId / systemId pair.

Further enhancements can be found within the Eclipse documentation

Inline Feedbacks
View all comments