Version 7.7.0 built on 2016-08-24.
Release Notes for Vaadin Framework 7.7.0
- Overview of Vaadin 7.7.0 Release
- Change Log for Vaadin 7.7.0
- Enhancements in Vaadin 7.7
- Incompatible or Behavior-altering Changes in 7.7
- Known Issues and Limitations
- GWT Dependency Changes
- Vaadin Installation
- Package Contents
- Migrating from Vaadin 6
- Vaadin 7.7.0 dependencies
- Upgrading to Vaadin 7.7
- Supported Technologies
- Vaadin on the Web
Overview of Vaadin 7.7.0 Release
Change Log for Vaadin 7.7.0
This release includes the following closed issues:
|#6346||LayoutClickListener doesn't work in FormLayout|
|#7103||IndexedContainerItem.getItemProperty should return null for non-existing properties|
|#7291||Check if gwtSdkFirstInClasspath should be used in archetypes|
|#8171||Check if LoginForm can be replaced by a less hackish solution|
|#8643||AbstractField doesn't fire ReadOnlyStatusChangeEvent when the read-only status of its data source changes|
|#9629||vaadin-archetype-application must not create empty widget set|
|#11450||AbstractField: getValidators() != null bad test|
|#12076||uitest war should not contain guava|
|#12214||Suboptimal default settings for generated pom.xml|
|#12351||Use @Inherited to simplify annotation management|
|#12397||Maven target should exclude gwt-UnitCache and symbolMaps in WAR file|
|#12653||Have predefined cache folders in Vaadin Maven archetypes|
|#13370||Tooltip (description) persists when moving mouse between portlets in Liferay|
|#13404||Move relevant default parameter values from Vaadin archetypes to plug-in defaults|
|#13584||Maven archetype vaadin-archetype-widget should use different folder naming|
|#13751||Integrate upstream maven plugin changes|
|#13917||Maven compile-theme: Support compilation of themes in src/main/resources|
|#14113||MarginInfo should have constructor with two booleans: vertical, horizontal|
|#14171||Artifact name conflict of Guava dependency|
|#14568||MenuBar click misbehaviour if submenu item is focused|
|#14735||Lots of warnings when compiling a project without theme or widget set|
|#14765||ListSelect keyboard selection broken in MultiSelect mode|
|#15489||Valo: Label.setEnabled(false) and Table.setColumnCollapsible("ColumnName", false) are not decorated accordingly|
|#16498||Can't remove shortcut listener from Panel|
|#16541||Better error reporting if container returns null itemId|
|#16792||README.md still mentions old devmode for client-side debugging|
|#17015||Widget archetype parameter should be componentClassName|
|Priority||#17169||com.vaadin.data.util.filter.Compare does not handle subclasses|
|#17485||Update plug-ins used by Maven archetypes|
|#17565||MarginInfo bitmask methods should be deprecated|
|Priority||#18418||Incorrect position of required indicators in slot|
|#18935||vaadin-maven-plugin is missing <jsInteropMode>|
|#19012||Maven plugin warning messages are too verbose|
|#19221||ComboBox sometimes clears "selection text" when selection popup is opened|
|#19396||Replace Atmosphere JQuery JS with the pure Atmosphere JS|
|#19427||ContainerOrderedWrapper.getItemIds return ids in the wrong order|
|#19445||Maven compile-theme: support all Sass compiler options|
|#19537||MessageSender makes an ambigous call|
|#19550||ListSelect doesn't render red border if validation fails|
|#19675||Vaadin should have a "default widgetset" to look for in the project|
|#19677||Newer GWT maven plugin sourceLevel defaults don't work|
|#19678||Automatically generate widgetset if needed|
|#19683||Use system parameters before application parameters|
|#19685||Limit ComboBox suggestion popup width to the component's width|
|#19690||Grid does not resize when row detail component is shown|
|Priority||#19742||NPE on Jetty 9.3 when closing tab with @Push(transport = Transport.WEBSOCKET_XH|
|#19749||Handle unknown attributes in DesignContext|
|#19766||TextArea.getCursorPosition() reports incorrect value when content is empty and using input prompt text|
|#19770||Make AppWidgetset support Spring Boot compatible|
|Priority||#19787||Can no longer re-select null item in NativeSelect|
|Priority||#19797||GridLayout row heights do not get equally distributed|
|#19805||Widgetset not found with 7.7-SNAPSHOT|
|Priority||#19809||Drag & Drop Fileupload broken|
|Priority||#19822||Push with no client request can exhaust the JVM heap|
|#19889||Fix old IE tests after merge of (#19658). Old IEs only.|
|#20001||Maven plugin does not look in correct repo for vaadin-client|
|#20026||Vaadin tries to create new Atmosphere threads after servlet context stop|
|#20031||Add null check to method 'setCellFocus'|
|#20038||Static inner classes are not supported by the declarative format|
|Priority||#20052||Scroller icon visibility issue in TabSheet within SplitPanel within TabSheet|
|Priority||#20104||TabSheet + Grid HeightMode.ROW size issue|
|Vote||Enhancements Vaadin support users have voted for|
|Priority||Defects Vaadin support users have prioritized|
You can also view the list of the closed issues at the Vaadin developer's site.
Enhancements in Vaadin 7.7
Vaadin 7.7 includes many major and minor enhancements. Below is a list of the most notable changes:
- Vaadin Framework is now built with Maven
- System properties can now override application properties, e.g. -DproductionMode=true (#19683)
- Vaadin can now automatically use default widgetset AppWidgetset optionally generated by the latest Vaadin Maven plug-in (#19675)
For enhancements introduced in Vaadin 7.6, see the Release Notes for Vaadin 7.6.0.
Incompatible or Behavior-altering Changes in 7.7
- Vaadin artifacts no longer bring a transitive dependency to javax.servlet:servlet-api.
- System properties now override application parameters for settings such as production mode (see above).
- The return type of BootstrapHandler.getWidgetsetForUI() has changed.
- Vaadin shared no longer depends on a custom build of Guava. Any project that depends on Guava as a transitive dependency should use standard Guava.
- Valo theme field error styles now apply to NativeSelect, ListSelect and TwinColSelect as well.
- The LoginForm component has been rewritten to better support auto-completion of passwords on modern browsers. Its API, look and DOM structure have changed somewhat, so any application level customizations of LoginForm need changes. See also #8171
- The way we handle GWT dependencies has been completely changed. See this section for more details.
- Client side compilation with Maven is now in strict mode by default, failing the compilation on any errors.
Known Issues and Limitations
- Vaadin TouchKit versions prior to 4.1.0 do not work with Vaadin 7.7. Please use version 4.1.0 or above.
- Context click events are not generated on iOS devices (#19367)
- Drag'n'drop in a Table doesn't work on touch devices running Internet Explorer (Windows Phone, Surface) (#13737)
It is currently not possible to specify font-size as em or %, or layout component sizes with em (#10634).
This does not apply to Valo, but using em sizes to size layouts is discouraged, because it results in fractional component sizes in many cases, which might cause unwanted 1px gaps between components.
- Up-to-date information about configuration needed for push and compatibility issues are available in
this wiki page.
The most prominent limitations are:
- Google App Engine has some limitations. Please consult Vaadin Wiki: Vaadin support for Google App Engine
- Grid does not support adding components to cells. Instead light-weight Renderers can be used to present and edit data.
GWT Dependency Changes
The GWT dependencies for Vaadin are now provided as actual dependencies and not bundled with Vaadin packages. This means that you can override the GWT version in your own project if you want to. Note that the GWT Elemental is still partially bundled with shared package to avoid having the gwt-user as a dependency everywhere.
- Basic Vaadin server-side only use does not need any changes to your project.
- Custom widgets and Add-ons should work just like before.
- Projects that use GWT RPC or other utils from the com.google package should add gwt-servlet dependency
<dependency> <groupId>com.vaadin.external.gwt</groupId> <artifactId>gwt-servlet</artifactId> <version>2.7.0.vaadin3</version> </dependency>
- OSGi currently does not work with client and client-compiler packages. Those should not be used with OSGi.
Vaadin is a Java framework for building modern web applications that look great, perform well and make you and your users happy. Vaadin is available under the Apache License, Version 2.0 (see the license.html in the Vaadin ZIP package).
The easiest ways to install Vaadin are:
- Maven dependency.If using Maven, define it as a dependency or use any of the available archetypes to create a new project. More information at https://vaadin.com/maven
- IDE Plugins.If using Eclipse, use the Vaadin Plugin for Eclipse, which automatically downloads the Vaadin libraries. For NetBeans 8.0 and 7.4, use the official Vaadin plugin that provides Maven based wizards and code completion support for Vaadin development.
Vaadin Framework is also available as a ZIP package downloadable from Vaadin Download page.
Inside the ZIP installation package you will find:
- Separate server-side (vaadin-server) and client-side (vaadin-client, vaadin-client-compiler) development libraries
- Precompiled widget set (vaadin-client-compiled) for server-side development
- Shared library (vaadin-shared) for both server- and client-side libraries
- Built-in themes (vaadin-themes)
- Dependency libraries provided under the lib/ folder
See the README.TXT in the installation package for detailed information about the package contents. Book of Vaadin (for Vaadin 7) gives more detailed instructions.
For server-side development, copy the vaadin-server , vaadin-client-compiled , vaadin-shared , and vaadin-themes from the main folder and the dependencies from the lib folder to the WEB-INF/lib folder of your Vaadin project. (The vaadin-client-compiled is necessary if you do not wish to compile the widget set by your own, which you need to do if you use almost any add-on components.)
Updates to the Packaging
Since Vaadin 7.2.0, the old vaadin-theme-compiler has been moved into a separate project and renamed to vaadin-sass-compiler. It is now included along with the other 3rd party dependencies in the ZIP package.
For pure client-side development, you only need the vaadin-client and vaadin-client-compiler JARs, which should be put to a non-deployed project library folder, such as lib . You also need them if you compile the widget set for any reason, such as using Vaadin add-ons, or create new server-side components integrated with client-side widgets.
Migrating from Vaadin 6
All Vaadin 6 applications need some changes when migrating to Vaadin 7. The most obvious changes are in the application/window API and require extending either UI or UI.LegacyApplication instead of Application. A detailed list of migration changes are given in the Vaadin 7 Migration Guide.
Any custom client-side widgets need to be ported to use the new client-server communication API, or the Vaadin 6 compatibility API.
Vaadin 6 add-ons (ones that contain widgets) do not work in Vaadin 7 - please check the add-ons in Vaadin Directory for Vaadin 7 support.
Vaadin 7.7.0 Dependencies
When using Maven, Ivy, Gradle, or other dependency management system, all Vaadin dependencies are downloaded automatically. This is also the case when using the Vaadin Plugin for Eclipse.
The Vaadin ZIP installation package includes the dependencies in the lib subfolder. These need to be copied to the WEB-INF/lib folder of the web application that uses Vaadin.
The dependencies are listed in the Licensing description. Some are explicit dependencies packaged and distributed as separate JARs, while some are included inside other libraries.
If you use the bean validation feature in Vaadin 7, you need a Bean Validation API implementation. You need to install the implementation JAR in the WEB-INF/lib directory of the web application that uses validation.
Upgrading to Vaadin 7.7
When upgrading from an earlier Vaadin version, you must:
- Recompile your classes using the new Vaadin version. Binary compatibility is only guaranteed for maintenance releases of Vaadin.
- Unless using the precompiled widget set, recompile your widget set using the new Vaadin version.
Remember also to refresh the project in your IDE to ensure that the new version of everything is in use.
By using the " ?debug " URL parameter, you can verify that the version of the servlet, the theme, and the widget set all match.
Eclipse users should always check if there is a new version of the Eclipse Plug-in available. The Eclipse Plug-in can be used to update the Vaadin version in the project (Project properties » Vaadin).
Maven users should update the Vaadin dependency version in the pom.xml unless it is defined as LATEST . You must also ensure that the GWT dependency uses the correct version and recompile your project and your widget set.
Liferay and other portal users must install the
Vaadin libraries in
Vaadin 7 is compatible with Java 6 and newer. Vaadin 7 is especially supported on the following operating systems:
- Mac OS X
Vaadin 7 requires Java Servlet API 2.4 but also supports later versions and should work with any Java application server that conforms to the standard. The following application servers are supported:
- Apache Tomcat 5-8
- Apache TomEE 1
- Oracle WebLogic Server 10.3-12
- IBM WebSphere Application Server 7-8
- JBoss Application Server 4-7
- Wildfly 8-9
- Jetty 5-9
- Glassfish 2-4
Vaadin 7 supports the JSR-286 Portlet specification and all portals that implement the specification should work. The following portals are supported:
- Liferay Portal 5.2-6
- GateIn Portal 3
- eXo Platform 3
- IBM WebSphere Portal 8
Vaadin also supports Google App Engine.
Vaadin 7.7.0 supports the following desktop browsers:
- Mozilla Firefox 18-47
- Mozilla Firefox 17 ESR, 24 ESR, 31 ESR, 38 ESR, 45 ESR
- Internet Explorer 8-11, Edge
- Safari 6-9
- Opera 16-37
- Google Chrome 23-52
Additionally, Vaadin supports the built-in browsers in the following mobile operating systems:
- iOS 5-9
- Android 2.3-5
- Windows Phone 8
Vaadin SQL Container supports the following databases:
Vaadin on the Web
- vaadin.com - The developer portal containing everything you need to know about Vaadin
- vaadin.com/demo - A collection of demos for Vaadin
- vaadin.com/learn - Getting started with Vaadin
- vaadin.com/forum - Forums for Vaadin related discussions
- vaadin.com/book - Book of Vaadin - everything you need to know about Vaadin
- vaadin.com/api - Online javadocs
- vaadin.com/directory - Add-ons for Vaadin
- vaadin.com/pro-tools - Commercial tools for Vaadin development
- vaadin.com/support - Commercial support for Vaadin development
- vaadin.com/services - Expert services for Vaadin
- vaadin.com/company - Information about the company behind Vaadin
- dev.vaadin.com - Bug tracker
- How to get the source code of Vaadin