Apache Wicket 6 Released With Integrated jQuery Support
The Apache Wicket project has released version 6.0.0 of its open source, component oriented Java web application framework. While this number is confusing at first glance since the last release was 1.5, in practice Wicket has just switched to Semantic Versioning for new development. Changes in the first digit are major changes that might break the public API, changes in the middle digit show backwards compatible additions in functionality and changes in the last digit show patch additions that only fix bugs.
A description of most of the changes are listed in the announcement, and more extensive details can be found in the migration guide. It is worth noting that while the previous version took more than 2 years in development, the 6.0.0 release happened after less than a year. This can be a sign of more frequent releases in the future development of Wicket.
Some of the most important changes for this version of Wicket are:
- Minimum requirement for Java 6
- Better alignment with JPA
- Package restructuring to easily accommodate OSGI support
- Wicket Resources can now define dependencies between them.
- Experimental support for websockets and integration with Twitter Bootstrap
- Several other improvements to AJAX control, feedback error messages, form validation etc.
Wicket 1.4 required Java 5 as a minimum. Wicket 1.5 required in addition a servlet container with support for version 2.5 of the servlet-api specification. With the present Wicket release Java 6 is the minimum version. This might force some legacy environments to upgrade their Java installation if Wicket 6 is to be used.
The iterator and other methods on IDataProvider, which is used in persistence, now has an argument of long instead of int raising the limits on item count that can be fetched.
Several package names have been changed in order to accommodate the usage of Wicket inside an OSGI container. Here is the list of name changes. A Wicket Resource now supports dependencies on other resources. Previously each resource was responsible for its own dependency management while now it delegates this effort to Wicket itself. Dependencies are resolved in the correct order in case of transitive links between them. Finally this version of Wicket offers experimental support (meaning that the API is not stable at all) for Websockets.
respect for Wicket
haiko van der schaaf
Many thanks for everybody contributing to Wicket.
David Beyer, Olaf Carlson-Wee, Richard Minerich Aug 02, 2015