Vaadin + Spring = AWESOME

This add-on adds support for Vaadin to Spring and Spring Boot, or Spring support to Vaadin, depending on your point of view ;-).

This project is not yet an official Vaadin Spring add-on, but a Vaadin R&D prototype that I work on whenever I have time. I'm also using the add-on in several customer projects to make sure it meets the requirements of a real-world project.

Quick start

There are three ways of getting this add-on. You can either clone this repository and build it yourself, download the latest release from Maven central, or download a snapshot from Sonatype. To build the add-on yourself, follow these steps:

1. Clone this repository: $ git clone https://github.com/peholmst/vaadin4spring.git
2. Change into the root directory of the working copy and run: mvn clean install

If you prefer to download the add-on from Sonatype, add this repository to your pom.xml file (please note that I currently push new snapshots to Sonatype manually, which means you might not always get the latest version):

<repository>
  <id>sonatype-snapshots</id>
  <url>https://oss.sonatype.org/content/repositories/snapshots</url>
  <snapshots>
    <enabled>true</enabled>
  </snapshots>
  <releases>
    <enabled>false</enabled>
  </releases>
</repository>

If you are downloading a release from Maven central, there is no need to add this repository.

When this is done, you need to create your actual application project. The easiest way is to go to http://start.spring.io and fill in the necessary details. Make sure you at least select the Web style. Then download the generated project as a Maven Project and open it up in your favorite IDE.

Now it is time to add this add-on. Add the following dependencies to your pom.xml file:

<dependency>
  <groupId>org.vaadin.spring</groupId>
  <artifactId>spring-boot-vaadin</artifactId>
  <version>[LATEST VERSION]</version>
</dependency>
<dependency>
   <groupId>com.vaadin</groupId>
   <artifactId>vaadin-themes</artifactId>
   <version>[LATEST VAADIN VERSION]</version>
</dependency>
<dependency>
   <groupId>com.vaadin</groupId>
   <artifactId>vaadin-client-compiled</artifactId>
   <version>[LATEST VAADIN VERSION]</version>
</dependency>

Finally, you can create your Vaadin UI. Create a new UI class in your project and annotate it with @VaadinUI e.g. like this:

@VaadinUI
public class MyVaadinUI extends UI {
    @Override
    protected void init(VaadinRequest vaadinRequest) {
        setContent(new Label("Hello! I'm the root UI!"));
    }
}

Run the main(String[]) method in the generated Application class and point your browser to http://localhost:8080 . Voila!

Configuring the Vaadin servlet

By default, the Vaadin servlet is mapped to /*. If you are only exposing your application as a web UI, this is good enough, but if you want REST endpoints as well, you need to change this mapping. You can do this by creating a file named application.properties in the src/main/resources directory and add the following property to it: vaadin.servlet.urlMapping=/myUI/*

The Vaadin servlet init parameters can also be configured in this way. Just prefix the name of the init parameter with vaadin.servlet.params.. For example, to turn on production mode, you would add vaadin.servlet.params.productionMode=true to the file.

Customizing the Vaadin servlet

If you want to customize the Vaadin servlet, just extend org.vaadin.spring.servlet.SpringAwareVaadinServlet and make it available as a Spring bean. The add-on will automatically discover your custom servlet and use that in place of the default servlet.

Serving static content

Static content from /VAADIN/* are served by a separate VaadinServlet that has no UIs at all. The servlet cannot be customized, but it can be configured in the same way as the Vaadin servlet (see above). The init parameters must be prefixed with vaadin.static.servlet.params..

If anybody wonders why a separate servlet is used, it was added after it became possible to use both TouchKit and "desktop" Vaadin in the same Spring application. Deciding which servlet to serve the static content was a bit tricky, so adding a separate servlet was the easiest solution. This might change in the future, if I come up with something better.

The UI Scope

This add-on provides a custom scope that binds the bean to the current UI instance. You can use it by adding the @UIScope annotation to the bean. The lifecycle of the bean will automatically follow the lifecycle of the UI instance, so you can also use @PostConstruct and @PreDestroy. Please note, however, that UI scoped beans cannot currently be ApplicationListeners. Also, no Vaadin components can be proxied.

The Vaadin Session Scope

This add-on provides a custom scope that binds the bean to the current Vaadin session. You can use it by adding the @VaadinSessionScope annotation to the bean. The lifecycle of the bean will automatically follow the lifecycle of the Vaadin session, so you can also use @PostConstruct and @PreDestroy. Please note, however, that Vaadin session scoped beans cannot currently be ApplicationListeners. Also, do not make any Vaadin components session scoped since a component can only belong to exactly one UI instance.

Navigator API integration

This add-on provides support for the Vaadin Navigator API. To use it:

1. Annotate your views with @VaadinView and make them either ui scoped or prototype scoped.
2. Inject an instance of SpringViewProvider into your UI and add it as a view provider to your Navigator instance.

Please see the JavaDocs and the sample application for more information.

The Event Bus

An Event Bus is oftend used to communicate change of state within the whole application or just within the UI. Vaadin4Spring provides a addon for this usecase.

More information can be found here.

Internationalization (i18n)

Internationalization in a Vaadin4Spring application is very much handled by the I18N features of Spring itself. However, to make it a bit easier to use, there is an addon, that provides a helper.

More information can be found here.

TouchKit Support

Initial TouchKit support has been added in the spring-vaadin-touchkit module. You can enable it by adding the module's JAR-file to your class path and adding the @EnableTouchKitServlet annotation to your Boot application class. If you want to enable the "desktop" Vaadin servlet as well, add the @EnableVaadinServlet annotation. In this case, remember to make sure the servlet's URL mappings are not conflicting. If you forget both annotations, only the servlet for serving static content will be registered and your application will not work.

TouchKit UI classes need to use the org.vaadin.spring.touchkit.TouchKitUI annotation to be detected by the UI provider.

You can configure the TouchKit servlet in the same way as the "desktop" Vaadin servlet, by using the touchKit.servlet.params. init parameter prefix. The URL mapping is specified using the touchKit.servlet.urlMapping parameter.

If you want to customize the TouchKit servlet, extend org.vaadin.spring.touchkit.servlet.SpringAwareTouchKitServlet and make it available as a Spring bean.

Finally, please note that TouchKit is a commercial Vaadin product. It can, however, also be used in AGPL projects.

Sidebar

The side bar can be used as a main menu in applications with many views. It is implemented as a Vaadin accordion and divided into sections. Every section contains clickable menu items. Both sections and menu items are added declaratively using annotations. More information can be found here

Security Support

Experimental

The Spring Security integration is still in very early stages of development. Do not assume it will work. More Information can be found here

Testing

Vaadin4Spring provides helpers to test UI scoped objects, especially when following the Model, Controller or Presenter patterns.

The testing module has its own README, you can find it here.