Version 7.6.0 built on 2015-12-28.
Release Notes for Vaadin Framework 7.6.0
- Overview of Vaadin 7.6.0 Release
- Change Log for Vaadin 7.6.0
- Enhancements in Vaadin 7.6
- Incompatible or Behavior-altering Changes in 7.6
- Known Issues and Limitations
- Vaadin Installation
- Package Contents
- Migrating from Vaadin 6
- Vaadin 7.6.0 dependencies
- Upgrading to Vaadin 7.6
- Supported Technologies
- Vaadin on the Web
Overview of Vaadin 7.6.0 Release
Vaadin 7.6.0 is a feature release that includes a number of new features and bug fixes, as listed in the list of enhancements and change log below.
Change Log for Vaadin 7.6.0
This release includes the following closed issues:
| #4200 | Pressing ESC-key in Firefox cancels active XHR-request causing Communication Problem | |
| Vote | #6914 | Event when a Table column is collapsed |
| #7449 | Serverside browser detection doesn't work on Weblogic Portal 10.3.2 | |
| Vote | #7717 | Allow HTML content in Tree captions |
| #9782 | Move VaadinSession storage logic to VaadinService | |
| Vote | #9811 | Non-collapsible columns should not be listed in the pop-up |
| #9953 | Properly initialize thread locals during HTTP session deserialization | |
| Vote | #10213 | UI needs a removeNavigator()-method |
| Vote | #11733 | Show a "reconnecting" dialog if the server connection is lost |
| Vote | #12518 | Make it possible to use XHR for actions initiated by the client even if push is enabled |
| #14006 | Allow instantiation of Vaadin Navigator with default constructor | |
| Vote | #14121 | Expose Push Connection state to Widget/Javascript |
| #14378 | Server Communication Progress/Error is not shown in push mode while in reconnect state. | |
| Priority | #14465 | Push transport does not reconnect or show error after computer sleep |
| #14555 | Update FontAwesome to version 4.4.0 | |
| #14716 | Use window.performance.now() in Profiler when available | |
| Priority | #14882 | NPE at FileUploadHandler.java:686 when the UI is already disposed |
| Priority | #16195 | Grid item IDs out of sync with container |
| #16348 | Doing "lazy init" in attach listener causes lots of "already registered" warnings | |
| Priority | #16465 | Push with longpolling: ui hangs for one minute on first click |
| #16597 | Column width are incorrectly calculated if there is a narrow column | |
| #16725 | Editor row validation and field validation are not in sync | |
| #16838 | Support column resize in Grid by dragging the header | |
| Priority | #16841 | Tab should only cycle through row fields in Grid editor |
| #16845 | There should be an option for using unconverted itemIds as caption in selection components. | |
| #16855 | Grid: Unable to listen to right click events on the client (for context menu) | |
| #16858 | Grid: Add context menu support | |
| #16918 | ComboBox scrolling broken on IE11 | |
| #16991 | Add "sortable" style to Grid header | |
| #17075 | Long polling connection tracking is incompatible with certain proxies | |
| Priority | #17301 | StringToEnumConverter fails with custom Enum.toString() implementations |
| Priority | #17383 | Window should not have ESC close shortcut hardcoded |
| #17519 | Boolean attributes are serialized inconsistently in to declarative format | |
| #17583 | True boolean attibutes should be 'margin' not 'margin=""' | |
| #17679 | Table rendering performance degradation since 6.8.13 | |
| #17917 | Refactor handling of focus and blur events in Connectors | |
| Priority | #17947 | Performance degradation when upgrading from 6.8.13 to 7.4.5 |
| #18317 | Make the framework detect hierarchy changes not sent to the client | |
| #18319 | Grid: expanding/collapsing the Details feels sluggish | |
| #18339 | deselectAll() method is needed in Grid | |
| #18456 | Accordion Tabs don't contain the set id | |
| #18472 | Extract theme font icons to a separate font | |
| #18481 | Support generated cell and row descriptions in Grid | |
| #18503 | Calls to container.indexOfId with SQL backend are expensive. | |
| #18510 | Omit empty hierarchy data from the response | |
| #18530 | setEnabled(false) in component container does not disable link in child Link component | |
| #18550 | Support defining a suspend timeout when using push | |
| #18624 | Grid SelectionModels should be extensions | |
| #18630 | AbstractRemoteDataSource does not inform properly on cache drop | |
| #18659 | Grid private nested class Sidebar has dead code | |
| #18663 | Grid row details can be opened even if no generator has been set | |
| #18692 | RowHandle pinning in AbstractRemoteDataSource does excessive RPC calls | |
| Priority | #18698 | Grid: CssLayout around the Grid cuts off Sidebar-Menu |
| #18703 | Slot of OrderedLayout on client side is final | |
| #18750 | Frozen grid non-editable columns misaligned in editor | |
| #18758 | Use of connection close in long polling causes excess tcp socket usage | |
| #18760 | Invalid (Finnish) month names shown in PopupDateField when using Java 8 | |
| #18782 | Round up to three decimal places values shown in the profiler section. | |
| #18787 | Valo Theme: FormLayout don't have separators when nested on a table on the first line | |
| #18809 | Moving the editor row does not save value | |
| #18811 | SingleSelectionModel default behaviour changed | |
| #18812 | Grid unbuffered editor does not display validation errors | |
| #18819 | Push connection hangs when interrupting the websocket connection | |
| #18831 | Grid misbehaves when selected items are filtered out | |
| #18838 | Add a style name to the body when reconnect dialog is shown | |
| #18908 | Grid has a validation error race condition | |
| #18909 | RpcDataSourceConnector throws when scrolling too fast | |
| #18919 | Grid editor should follow focus based on events from the user | |
| #18956 | Grid editor opening does not always handle internal cell focus correctly | |
| #18959 | Grid editor move twice too fast throws an exception | |
| Priority | #18987 | Primary style name is null for number of components |
| #18989 | Support defining the URL to use for push requests | |
| #18998 | Store VaadinSession as APPLICATION_SCOPE in portals | |
| #19007 | PortletSession is missing methods for scoped methods | |
| #19009 | "Communication error" in Liferay 6.2 CE GA4 when using IE | |
| #19015 | Components should support context click events | |
| #19017 | Unable to override ConnectionStateHandler without extending DefaultConnectionStateHandler | |
| #19024 | Make debugging widgetset splitting easier | |
| #19034 | Report total app bootstrap time in the debug window | |
| #19038 | DataGenerators occasionally want to get rid of old data | |
| #19042 | Extend ContextClickEvent support to have a specific event for table | |
| #19056 | TreeTable should support context click events | |
| #19062 | Tree should support context click events | |
| #19092 | Undeprecate and document VaadinPortletSession | |
| #19096 | Checkbox in Grid Editor does not change value | |
| #19128 | Grid should support context clicks in empty areas | |
| #19130 | Table and TreeTable should support context click events in empty area | |
| #19141 | Grid headers and footers are misaligned in Runo theme | |
| #19152 | De-selecting a row that is already removed from container causes NPE | |
| Priority | #19201 | Websocket reconnect fails when killing the wifi connection |
| #19206 | Add ContextClickEvent for long touches. | |
| #19222 | Improve Longtouch context menu behaviour on iOS. | |
| #19227 | Specify custom first day of week for Calendar | |
| #19302 | MultiSelectionModel setSelected does not update on the client | |
| #19322 | Select all checkbox is not correctly updated | |
| #19323 | Upgrade to Atmosphere-js 2.2.13 | |
| Priority | #19357 | Grid selection disappears when sorting |
| Priority | #19359 | Grid selection does not apply when you change the visibility |
| Priority | #19360 | Grid keeps item selected when you unselect |
| #19364 | Grid: cellClassGenerator fails if its returns an empty string | |
| #19367 | Context click should not select text | |
| #19368 | Enable using custom overlay in VMenuBar | |
| #19371 | RpcDataProvider does not recreate value change listeners on ItemSetChange | |
| #19388 | Javascript error when browser goes online | |
| #19389 | Unbuffered editor focus handling broken in IE8 | |
| #19391 | Websocket does not reconnect after Firefox/Safari goes offline and online again | |
| #19394 | Unable to set boolean configuration values for push through UI | |
| #19408 | Context click on the resize handle gets handled by the wrong cell | |
| 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.6
Vaadin 7.6 includes many major and minor enhancements. Below is a list of the most notable changes:
- New configurable client-server automatic reconnect handling and warning dialogs
- Grid columns can be resized by the user
- Grid non-modal editor mode and unbuffered datasource binding
- More fluent Grid scrolling for touch devices
- Better customizability of Grid (data generators for communication, customizable selection models etc.)
- Configurable keyboard, touch and mouse navigation support for Grid editor
- Declarative HTML serialization enhancements for Vaadin Designer 1.0
- Better handling of closing a window with keyboard shortcuts
- Column collapsing events for Table
- Most Components fire a ContextClickEvent when the user tries to open a context menu. This event is specialised to contain some extra context for Grid, Table, TreeTable and Tree, and used by the ContextMenu add-on.
- New push transport mode WEBSOCKET_XHR (WebSockets from server to client, XHR from client to server) which allows setting of cookies, using request scopes with CDI/Spring etc.
- Navigator is more extensible and can be used with dependency injection
- It is possible to customize the push URL using PushConfiguration.setPushUrl(). This enables implementing some push related add-ons such as push on portals.
For enhancements introduced in Vaadin 7.5, see the Release Notes for Vaadin 7.5.0.
Incompatible or Behavior-altering Changes in 7.6
- Window.setCloseShortcut() is now deprecated. ESCAPE is no longer a hard-coded default, but rather a soft one, and can be removed. If the close-shortcut attribute of the v-windowelement is present, it must list all close shortcuts, including ESCAPE, separated by whitespace. Existing, unchanged code should behave as before. See ticket #17383 for more information on the reasoning behind the change.
- Grid SelectionModels are now Extensions. This update removes all selection related variables and API from GridConnector, GridState, GridServerRpc and GridClientRpc
- StringToEnumConverter now explicitly supports Enum types with custom toString() implementations. This may affect applications that relied on the undefined behavior in previous versions.
- The Section enumeration from client-side of the Grid has been moved to GridConstants
- The order in which AttachEvents are fired has been changed. When attaching a component with child components, events are now fired first for the children and last for the root component. The order is thus the same as the order in which custom code in overridden Component.attach methods would be executed. Please refer to ticket #16348 for more information on this change.
- Jsoup library version 1.8.3 is incompatible with the version 1.8.1 used in early 7.6 alphas and 7.5. This might cause problems with external libraries compiled against said versions.
- Declarative format is now using "vaadin-" as a default prefix instead of the "v-" prefix used in 7.5. This default can be changed in deployment configuration.
Known Issues and Limitations
- Vaadin TouchKit versions prior to 4.1.0 do not work with 7.6. 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.
Vaadin Installation
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 or JAR package).
The easiest ways to install Vaadin are:
- Maven dependecy.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.
Package Contents
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.6.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.
Bean Validation
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.6
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
Supported Technologies
Vaadin 7 is compatible with Java 6 and newer. Vaadin 7 is especially supported on the following operating systems:
- Windows
- Linux
- 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.6.0 supports the following desktop browsers:
- Mozilla Firefox 18-43
- Mozilla Firefox 17 ESR, 24 ESR, 31 ESR, 38 ESR
- Internet Explorer 8-11, Edge
- Safari 6-8
- Opera 16-34
- Google Chrome 23-47
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:
- HSQLDB
- MySQL
- MSSQL
- Oracle
- PostgreSQL
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