Tapestry 5.7.0 is a new major version which needs a migration step for projects using previous versions. To upgrade, update the dependency in your build configuration (Maven POM, Gradle build script, etc.) – or Download the new JAR file. Please check the Upgrade Guide section below for details. This is a step that only needs to be done once. Please also review the How to Upgrade instructions before upgrading.
The main new features are:
- Partial Java 9+ modules (JPMS) support. It's partial because module-info.java classes are not provided yet. On the other hand, Tapestry's JARs don't have split packages anymore, making them easier to be used with Java 9+ modules. Many classes had to be moved to other packages, and sometimes even to a different JAR. The migration tool mentioned above will take care of updating your code so it uses the correct new fully-qualified class names for the ones that were moved and/or renamed.
- TypeCoercer now uses mapped configuration so coercion overrides are done in an explicit manner.
- TAP5-2650 - Getting issue details... STATUS
- It's not possible to use the Tapestry request handling framework, specially the RequestFilter, Dispatcher, Request, Response and HttpServletRequestFilter classes, without the page framework. These classes were moved to a new artifact, tapestry-http, which can be used in place of tapestry-core (which depends on tapestry-http). tapestry-http Servlet filter class is org.apache.tapestry5.http.TapestryFilter. The original TapestryFilter, from org.apache.tapestry5, can be used in the same way way as in past Tapestry versions.
5.7.0 Upgrade Guide
The first step is running the source code migration tool:
- Download the migration tool jar from https://repo1.maven.org/maven2/org/apache/tapestry/tapestry-version-migrator/5.7.0/tapestry-version-migrator-5.7.0.jar
- Run "java -jar tapestry-version-migrator-5.7.0.jar upgrade 5.7.0" (without quotes) in the command line. It will process all .java files found in the current folder and its subfolders, recursively.
The second step is updating how contributions to the TypeCoercer service in case your projects have them. Here's a real example from Tapestry itself. It used to be done using Configuration, but now it's MappedConfiguration. If you had a contribution method like this:
@Contribute(TypeCoercer.class)
public static void provideCoercions(Configuration<CoercionTuple> configuration)
{
configuration.add(CoercionTuple.create(String.class, JSONObject.class, new StringToJSONObject()));
}
it should be changed to this:
public static void provideCoercions(MappedConfiguration<CoercionTuple.Key, CoercionTuple> configuration)
{
CoercionTuple<String, JSONObject> stringToJsonObject = CoercionTuple.create(
String.class, JSONObject.class, new StringToJSONObject());
configuration.add(stringToJsonObject.getKey(), stringToJsonObject);
}
Improvements made
Bugs fixed