Release lines

Apache Wicket 6.x

Out of service: no more releases, not even security fixes.

Latest release
6.30.0
Status
End of life
Supported
No longer supported
Java
6 or newer
Servlet API
Servlet 2.5 or newer

Move to a line in service: the upgrade paths show the route from Wicket 6.

Maven dependency

<dependency>
    <groupId>org.apache.wicket</groupId>
    <artifactId>wicket-core</artifactId>
    <version>6.30.0</version>
</dependency>

New in Wicket 6

  • Java 6

    Wicket 6 requires Java 6 and Servlet 2.5.

    Java
    6
    Servlet
    2.5

  • Ajax built on jQuery

    The Ajax library is reimplemented on jQuery, which makes jQuery plugins easy to integrate. Ajax components register browser events instead of writing inline event attributes, so a tag can have several listeners and the markup stays clean.

  • Control over every Ajax request

    AjaxRequestAttributes lets you change any aspect of an Ajax request: the HTTP method, multipart submission, throttling and more.

    SaveBehavior.java

    @Override
protected void updateAjaxAttributes(AjaxRequestAttributes attributes) {
    super.updateAjaxAttributes(attributes);
    attributes.setMethod(AjaxRequestAttributes.Method.POST);
}

  • Resources with dependencies

    A resource can declare what it depends on, such as a jQuery plugin on jQuery, and Wicket renders the dependencies in the right order. In deployment mode packaged resources switch to their .min.js versions automatically.

  • Large datasets

    IDataProvider uses long instead of int for indexes and sizes, lining up with the Java Persistence API.

Documentation

News about Wicket 6

All posts on the blog

Download

The most recent release in this branch is: 6.30.0.

You can get the release using Maven or download it manually.

Download manually

Use the following links to download Wicket manually to build Wicket from source:

Or use the following links to get the pre-packaged binaries instead:

Note that the binary packages and the source packages don’t contain any dependencies necessary to have your project working out of the box. We strongly urge you to use Maven (or Buildr, or Gradle) as your dependency management system.

Older releases

The Apache mirroring system only hosts the latest version of each actively supported branch. When you need to download an older release you can find them in the archives.

Go to the Apache archives to find your specific version.

Change log

To see what changed in this release (and prior releases) you can read the change log.

Requirements

Apache Wicket has few requirements in order to work properly. In this section you’ll find the minimum requirements for all Wicket modules. Specific modules may need additional libraries, such as file upload, date time APIs, CDI specifications, and more. See the module’s POM for more details on the necessary libraries.

Java version

This Wicket version requires at least the following Java version: JDK 6.0 or newer.

Not only is a particular version of Java necessary, Wicket also needs access to specific APIs.

Servlet API

This Wicket version requires at least the following Servlet API version: Servlet API 2.5 or newer. This is provided by your container, please see the documentation of your container to see which version of the Servlet specification is supported.

In addition to the Servlet API, Wicket uses SLF4J to let you choose your own implementation of a logging framework.

Logging

You cannot use Wicket without adding an SLF4J logging implementation to your classpath. Most people use log4j.

If you do, just include slf4j-log4j12.jar on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the SLF4J site for more information.

Don’t mix Wicket versions

You cannot mix different Wicket versions in your project. You should always use the artifacts from a particular release. For example it is not possible to use Wicket Extensions 1.5 in a Wicket 6 project, or Wicket CDI 6.19 in a Wicket 7 project. The same goes for 3rd party libraries: make sure you always use a compatible version of your 3rd party library.

Migrating from earlier versions

If you are migrating an existing application from earlier versions of Wicket you may find our migration guides invaluable: