Over a million developers have joined DZone.

Migrating to Vaadin 8

DZone 's Guide to

Migrating to Vaadin 8

Vaadin 8 has a compatibility layer to ensure your work with Vaadin 7 will carry over. If you want to remove it, you'll need to work with the DataBinding API.

· Java Zone ·
Free Resource

Today I finished my migration of a (small) demo app to the new Vaadin 8 API.

First of all: Vaadin 8 has a compatibility layer. Everything you may have used with Vaadin  7 will still work with Vaadin 8, you just have to change some package names in your import statements. (for example, UI gets ui.v7) and everything will work out of the box with Vaadin 8.

But my goal was to completely remove the compatibility layer. That needed quite a bit of work, as the new DataBinding API focuses on binding bean properties. My app used the PropertySetItem in a bunch of places. To move these, I created backing beans and used the new API.


This was not too hard, but there was more work to be done, as I had to migrate all of my custom Validator implementations. The new Validator signature tastes better than the v7 one, but changing them introduces even more work:

class PasswordMatchValidatorV8 constructor(private val src: PasswordField) : 
    Validator<String> {

    override fun apply(value: String, ctx: ValueContext): ValidationResult {
        val pw: String = src.value        
        if (pw != value) {
            return ValidationResult.error(NO_MATCH)
        return ValidationResult.ok()

    companion object {
        const val NO_MATCH = "Passwords don't match"    }

That did make up for most of the fields. Another place where I had to change the code was the old BeanItemContainer, which I used to bind collections to grids etc. Here we have new API too that looks like this:

grid = Grid()
grid.addColumn{ u -> u.email }.setCaption("Username")
dataProvider = ListDataProvider(users)
grid.dataProvider = dataProvider

That's it. It took me about a day for nine View Classes, but remember I was very slow getting used to the new binding style.

For my personal taste, the new binding API is a great step forward, and it makes heavy use of SAM types. Using it with Kotlin is a breeze. It's is still far away from beeing as powerful as the good old eclipse DAtaBinding API, which is still my personal favorite when it comes to UI data bindings.

vaadin ,java ,kotlin ,tutorial ,data binding

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}