There is a Maven Plugin available for Vaadin platform. It handles transpilation, minification and bundling of the front-end resources for the production version of the application. This is only necessary for when you take the application for production, or want to test it with IE11.
There are no custom widgetsets or Sass themes that need compilation for development time in Vaadin platform. The plugin is thus not needed during development, except when testing with IE11.
There are no archetypes available for Vaadin platform. Please visit vaadin.com/start for available starting points. There you can find Maven-based example applications and project bases available for Vaadin platform.
Vaadin platform has an integration for using it with Spring.
The concept is mostly the same, but some features like the
@ViewScope have been removed.
Also there are currently no specific Spring Security support, but it can still be integrated manually.
The Bakery App Starter for Flow and Spring shows an example of this.
There is a CDI Add-on enabling JEE features. This is currently part of Vaadin platform starting with V12 and also compatible with V10.
In Vaadin 8, Designer was used to edit declarative files with a
.html suffix. Despite the file format suffix, the declarative format was a generic XML syntax that mapped directly into a tree of Vaadin components on the server side. The XML was read by Vaadin at runtime on the server, and was never sent to the client. It’s important to note that the syntax only allowed component declarations.
Some features of Designer are only available for Vaadin platform and other features can only be used when editing Vaadin 8 layouts. See the Release Notes for an overview of the feature-level differences.
As the underlying technology has been completely changed, Vaadin 8 Designs are not compatible with Flow applications.
There are two paths to migration; either use the upcoming Multiplatform Runtime from the Prime subscription to run a Vaadin 8 application inside a Vaadin platform application,
or migrate the HTML files manually. When migrating manually, the declarative component tree should be copied inside the
<template> in a blank Vaadin platform design,
and then modified to fit the new element API’s.
The same features exist in TestBench for Vaadin platform as in TestBench for Vaadin Framework 8 but the API has been tweaked in many places to be in sync with corresponding changes to the components/elements and the features they offer.
The ElementQuery operation
$ no longer has methods such as
caption() as there is no generic "caption" concept in Vaadin platform. On the other hand, there is instead a generic
attribute(String key, String value) method which can be used to find elements based on any HTML attribute.
The element classes have been moved to a sub package of the component, e.g.
com.vaadin.flow.component.textfield.testbench.TextFieldElement instead of
If any API is missing, there are low level helper methods available such as
TestBenchElement.getProperty(String name) and
Vaadin Board for Vaadin platform contains the same API as Vaadin Board for Framework 8 but the API has been adapted to follow Flow/Vaadin platform conventions, e.g.
add(Component… component) instead of