Vaadin 20.0.2

Vaadin consists of a set of web components, a Java web framework, configurable themes, tools and a set of app templates.

This is a maintenance release of Vaadin.
See the full release notes for vaadin 20.0 in GitHub releases, including new features, getting started, supported browsers and other technologies, and migration notes.

Visit vaadin.com to get started.

New and Noteworthy

Here are the highlighted new and improved features in this maintenance release.

Vaadin Flow (7.0.2)

• Fixes:

  • ⧉ Handle concurrent file requests (#11147). PR:11155. Ticket:11144

    Fixes a regression in Flow 7.0 / Vaadin 20.0 that broke resources loading

  • ⧉ Keep package.json ordered (#11179). PR:11199. Ticket:7431

  • ⧉ Apply theme correctly even when no Vaadin components are used (#11211). PR:11216

  • ⧉ NumberModel should read empty string as undefined (#11169). PR:11174

    NumberModel should read empty string as undefined so that the NumberValidator can pass the validation for an option number field when the input value is an empty string.

  • ⧉ Add javadocs warning to avoid using ResponseWriter for dirs (#11112). PR:11163

Spring Addon

• fix: annotate default error handler
  • _Annotate SpringRouteNotFoundError with DefaultErrorHandler so that users can make custom error views for NotFoundException.
• fix: put and use app context as a servlet context attribute
  • Fixes a regression in Vaadin 19 + 20 with Vaadin & SpringMVC applications. This fix was originally done to Vaadin 14 but was not forward ported to latest version until now.

Support

vaadin 20 is supported for one month after Vaadin 21 has been released. The latest LTS (long term support) version is Vaadin 14. More details of our release model are available on our roadmap page.

Vaadin also provides commercial support and warranty.

Getting Started with Vaadin

App starters

The best way to get started with Vaadin is to go to https://start.vaadin.com and configure your new application by setting up your views, entities, styles, and the technology stack you’re interested in.

For the full list of how to get started go to the GitHub releases.

Reporting Issues

We appreciate if you try to find the most relevant repository to report the issue in. If it is not obvious which project to add issues to, you are always welcome to report any issue at https://github.com/vaadin/platform/issues.

A few rules of thumb will help you and us in finding the correct repository for the issue:

1. Bug tickets and enhancement requests that are specific to a certain Vaadin component should be posted in the component's Web Component repostory (e.g. https://github.com/vaadin/vaadin-button for Button).
2. Issues that are not component-specific (e.g. requests for new components) or encompass multiple components should be posted in vaadin-flow-components repository.
3. If you encounter an issue with Flow which does not seem to be related to a specific component, the problem is likely in Flow itself. The Flow repository is https://github.com/vaadin/flow
4. If you encounter an issue with Designer, the repository is https://github.com/vaadin/designer
5. If you encounter an issue with TestBench, the repository is https://github.com/vaadin/testbench