Apache Wicket 8: Write less, achieve more with this Java framework
It’s been a while since we last checked in on Apache Wicket, but news this week shows Wicket 8 is finally here. What’s new about this serverside Java framework? Java 8 support, Lambdas, and more!
Wicket is an open source, component oriented, Java web application framework with over a decade of experience. So, it’s exciting to see a new update from the Wicket team. What’s new in Wicket 8? No rewrites necessary, just the ability to write less and do more.
Previously, developers could use Java 8 and above for their projects. But now, Wicket 8 has full and complete support for all Java 8 idioms, meaning developers can use lambda expressions wherever they want. The current API fully supports all of the idioms and types you know and love from Java 8, and it’s the minimum requirement for all Wicket projects.
Of course, this means lambdas! Despite any performance or memory usage issues, lambdas are a can’t miss feature for Java. Subclassing is still the primary extension mechanism for Wicket components.
However, factories for lambdas have been provided for various forms of models, like databinding, and behaviors, like adaptors for components. Wicket uses models as the databinding method. Every data-aware component is able to take a model implementation and use it to retrieve and store data. Now, developers can use lambdas wherever they can use models.
Java 8’s Optional type is allowed in Wicket 8, specifically for places in your API where things can be null. In Wicket 8, it’s used to clarify the API. Since this is modified from the original usage in Java 8, you may run into compile errors if you use optional type and migrate to Wicket 8.
Wicket 8 also provides support for the new ways to handles dates and times in Java 8, no matter what format.
Get Wicket 8