Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This is the consolidated list of changes between Tapestry versions 5.2 and 5.3. To upgrade from 5.2 to 5.3, most users who are not using deprecated features will be able to just update the Maven dependency in their POM file (or download the new JAR file) and the new version will just work. However, please read carefully below before upgrading.

Breaking Changes

Tapestry now depends on Servlet API version 2.5 (prior releases worked with 2.4).

Tapestry no longer supports the ability to inject the component id into a String field. This was rarely (if ever) used functionality that caused unwanted conflicts elsewhere. When a component needs to know its component id, it may inject the ComponentResources object, and invoke getCompleteId().

Many classes and interfaces that were deprecated in prior releases of Tapestry have been removed in Tapestry 5.3. See the full list. As always, you should use your IDE to find and replace all deprecated items before you upgrade. The following are the most significant of these:

...

Tapestry applications now include a built-in "PageCatalog" page, which lists all the loaded pages of the application, with details about construction time and number of components. The page requires whitelist access (see above comment), and some functionality is only available in development mode. PageCatalog can be used to load all pages of your application, which is useful to quickly spot problems in your pages (especially useful when upgrading from a prior release of Tapestry).

Quickstart Archetype Improvements

The Maven Quickstart Archetype has been improved; it now demonstrates many more features of Tapestry. In addition, it constructs a Gradle build.gradle file for the created project.

Removed Functionality

The integrated Blackbird client-side console has been removed. In its place are the floating console messages (used when Blackbird is disabled) combined with logging to the Firebug or WebKit console. This should make debugging client-side JavaScript much easier. In addition, Tapestry will now display a pop-up window containing the full exception report for a server-side error that occurs during an Ajax request.

...