Vaadin 14.4.9
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 14.4 in GitHub releases, including new features, getting started, supported browsers and other technologies, and migration notes.
Visit vaadin.com to get started.
Support
Vaadin 14 is an LTS (long term support) version, which will be supported for 5 years after the GA (general availability) release. More details of our release model are available on our roadmap page.
Vaadin also provides commercial support and warranty.
New and Noteworthy
Here are the highlighted new and improved features in this maintenance release.
Vaadin Flow (2.4.7)
-
Fixes:
-
⧉ Options in the Combo Box's selection list are consistent and not disappearing when first searching and then selecting them. This was happening while using Combo Box with a ComponentRenderer. (#9783). PR:10054. Ticket: vaadin/flow-components#437
-
⧉ No exception would be thrown if servlet class cannot be loaded. This means no more
ClassNotFoundExceptionbyDevModeInitializerwould be thrown for builtin servlets in containers such as Wildfly (#8233). PR:10041. Ticket:8149 -
⧉ Importing binary files (e.g. images) in a frontend file (e.g. TS file) and would not result into
MalformedInputExceptionduring startup (#9955). PR:9961. Ticket:9926 -
⧉ Always write the package json after updateDefaultDependencies as even if the dependencies are not updated the defaults may be updated. PR:10081. Ticket:10032
-
-
Behaviour changes:
- ⧉
Element::removeAllChildrenbehaviour has been changed (#10128) so that the re-attached node persists its state "removed children" between client-server roundtrips. It wasn't a case before that change, the "clear all" event happens only once after first attach of the node.
That effectively means that if you have a client-sideLitElementcomponent and correspondingLitTemplatejava-side component, then once you callElement::removeAllChildrenon java-side, it will remove all children on client-side on every attach action. Ticket:10119
- ⧉
Vaadin Spring Addon (12.3.3)
-
Fixes:
-
Add
org.eclipse.persistenceto default exclusions as it is a common transitive dependency that easily adds tens of seconds to the startups time. (#674) -
Expose Spring executor for Vaadin dev mode as part of fixes made for resolving the problem of leaving
pnpmandwebpack-dev-serverrunning after Spring Boot stopped (#692). -
Get all executor beans instead of one bean via getBean to solve the startup failure due to use
@EnableSchedulingin applications based on Spring Boot(#701).
-
Changes since 14.4.8
Getting Started with Vaadin 14
App starters
The best way to get started with Vaadin 14 is to go to https://vaadin.com/start and pick an app template for 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:
- 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).
- Issues that are not component-specific (e.g. requests for new components) or encompass multiple components should be posted in vaadin-flow-components repository.
- 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
- If you encounter an issue with Designer, the repository is https://github.com/vaadin/designer
- If you encounter an issue with TestBench, the repository is https://github.com/vaadin/testbench