Wicket components and utilities that uses functional features from Java 8
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src
.gitignore travis container based builds, gitignore Apr 3, 2015
.travis.yml
README.md Update README.md Aug 13, 2014
pom.xml Jacoco maven plugin version update Jul 31, 2014

README.md

Lambda Model

Build Status Coverage Status

Lambda Model is replacement for usual PropertyModel. It tries to be as simple as possible to write, ensure type safety and keep code short and readable. To achieve this, lambda model uses lambda expressions from Java 8.

IModel<String> model = new LambdaModel<String>(getterExpression, setterExpression);

Why to replace PropertyModel at first place? Property Model works fine, it's easy to write, easy to understand and code is short. But it has several problems. Mainly it is not type safe and not refactoring friendly. And that is something you really don't want in Java code. For example suppose we have object person of type Person with property name of type String. Then property model looks like this:

IModel<String> nameModel = new PropertyModel<String>(person, "name");

Everything works well, it is short and elegant. But one day you decide that name should not be String, rather object of type Name, with properties firstName and lastName. Your IDE will help you to refactor code. But compiler and IDE has no chance to recognize, that old PropertyModel is now accessing different type and will return wrong data (probably toString of object).

Or you decide to rename property (and getter and setter) to fullName and error is introduced. Compiler will not check that old property name does not exist anymore. This and other problems of PropertyModel are also descibed in article A CLEAN APPROACH TO WICKET MODELS by @trautonen.

Lot's of people are dealing with this problem and looking for a way how to ensure type safety while keeping symplicity of PropertyModel. For example project SafeModel uses proxy and reflection to remove string-typed properties. In Scala extensions you can find pretty much the same implementation as this LambdaModel. It's called Fodel and uses the same getter and setter passing.

LambdaModel takes different approach then reflection. It tries to be as simple as possible and avoid all the magic. With Java 8, we can use references to methods or short and easy to read lambda expressions. Model, that access property name of object person can be written in this form:

IModel<String> nameModel = new LambdaModel<String>(person::getName, person::setName);

Model is typesafe, IDE knows about usage when you refactor, compiler will fail if you rename getter and forgot to update model. There is no such thing as "string encoded" property anymore and no reflection behind scene. You can provide your getter and setter as a lambda expressions. That gives you power to access nested objects:

final IModel<String> model = new LambdaModel<>(()->person.getChild().getName(), (val)->person.getChild().setName(val));

Implementation is based on Supplier and Consumer functional interfaces from Java 8.

Main benefits are: no magic, type safety, easy refactoring. Current known limitation is possibility to provide getter different from setter and access two different properties. There is nothing to prevent it. But on the other hand it will help you to write simple models for objects, that are not pure POJOs.