Version 7.4.1 built on 2015-03-06.

Release Notes for Vaadin Framework 7.4.1

Overview of Vaadin 7.4.1 Release

Vaadin 7.4.1 is a maintenance release that includes a number of new bug fixes, as listed in the change log below.

Change Log for Vaadin 7.4.1

This release includes the following closed issues:

#13248Client does not disconnect push properly when UI is closed by server
#15317Session expired when UI is locked causes infinite loop with Push (polling) enabled
#15330Vaadin calling close() on atmopshere with WEBSOCKET when a connection times out
Priority#15352Unable to focus a field with an error indicator (iPhone)
Priority#15353Unable to dismiss a tooltip on an iPhone
#15551Validate and fix declarative support for AbstractEmbedded
#15552Validate and fix declarative support for Image
#16220Detaching and re-attaching a Grid causes scroll position to be lost (and no data to be shown)
#16325Validate and fix declarative support for BrowserFrame
#16327Validate and fix declarative support for Flash
Priority#16486Unsteady appearance of modal window dialog when pre-selecting multiple items in List Select
#16511Grid disappears if it does not have caption and gets an error indicator
#16523Vaadin Calendar readOnly mode prevents from clicking
#16539Column widths are not recalculated when enlarging a Grid
#16550"Value change listeners not set up correctly" Exception
#16559NullPointerException when setting Grid ContainerDataSource
Priority#16563Sorting by empty arrays should always clear the sorting indicator.
#16565Scrolling Grid in Chrome broken
Priority#16583DesignContext is not OSGi compatible
#16592NPE VaadinService.createCriticalNotificationJSON
Priority#16611Problem while reloading a table with widgets inside
#16614Fix Grid's row width calculation workaround
Priority#16650runWebkitOverflowAutoFix doesn't restore overflow correctly
#16651A UI which throws an exception during setSession(null) is never cleaned up
Priority#16677In IE DateField doesn't fire ValueChangeEvent on press of Enter or Return
#16696The transition-property mixin of Valo causes a parse error
#16724Restore link in release notes
#16726Grid.Column.setLastFrozenColumn does not work
#16739Vaadin-server bundle missing import of guava bundle
Priority#16747Removing and adding rows cause an infinite loop in the browser
#16748Method to ask Grid to recalculate the column widths
#16750Grid rendering slows down considerable when adding more than 50 columns.
#16762Grid scrolls in the wrong direction
#16776Slider.setMin(value) throws Slider$ValueOutOfBoundsException
#16805vaadin-widgets-7.4-SNAPSHOT-sources.jar does not have sources
#16825Duplicate resource warnings logged by push in 7.4
#16826NPEs logged by Push when running on Tomcat 7
#16832Replacing container of Grid brakes scrolling
#16852There are no scrollbars in Grid on Mac if you do not have scrollbars always on
#16862Potential problem of writing to recycled requests
#16868Application should stop running if a communication error occurs
#16900Grid column widths reset after changes that trigger column relayout
#16905RpcDataProvider sends rows in random order when adding and modifying
Priority#16924Widget set cannot be loaded with Windows Phone 8.1 GDR1
#16938Push disregards custom CommunicationErrorHandlers
#16951Exception during request lost if an exception happens during writing of UIDL error message
#16964LayoutManager measureConnector could reuse element object
#16968ApplicationConnection hierarchy checking could be faster
#16993Widgetset sub directory missing from OSGi manifest
 
VoteEnhancements Vaadin support users have voted for
PriorityDefects 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.4

The 7.4 includes many major and minor enhancements. Below is a list of the most notable changes:

For enhancements introduced in Vaadin 7.3, see the Release Notes for Vaadin 7.3.0.

Incompatible or Behavior-altering Changes in 7.4

Known Issues

Limitations

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:

It is also available as a ZIP package downloadable from Vaadin Download page.

Package Contents

Inside the ZIP installation package you will find:

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.)

For compiling the widget set, for instance when using Vaadin add-ons with custom client-side implementation, you need to include vaadin-client and vaadin-client-compiler on the compiler classpath. Those JARs should be in a non-deployed project library folder, such as lib.

Updates to the Packaging

Vaadin 7.4.0 introduces vaadin-widgets for pure client-side development. This JAR only contains GWT Widgets designed to be fully functional without Vaadin's server-side.

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.4.1 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.4

When upgrading from an earlier Vaadin version, you must:

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 ROOT/WEB-INF/lib/ in the portal (and remove a possibly obsolete older vaadin.jar). Additionally, the contents of the vaadin-client-compiled and vaadin-themes must be extracted to the ROOT/html/VAADIN directory in the Liferay installation. If your portal uses custom widgets, you can use Liferay Control Panel for Vaadin for easy widget set compilation.

Notes and Limitations for Google App Engine

The following instructions and limitations apply when you run a Vaadin application under the Google App Engine.

For other known problems, see open tickets at developer site dev.vaadin.com.

Supported Technologies

Vaadin 7 is compatible with Java 6 and newer. Vaadin 7 is especially supported on the following operating systems:

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:

Vaadin 7 supports the JSR-286 Portlet specification and all portals that implement the specification should work. The following portals are supported:

Vaadin also supports Google App Engine.

Vaadin 7.4.1 supports the following desktop browsers:

Additionally, Vaadin supports the built-in browsers in the following mobile operating systems:

Vaadin SQL Container supports the following databases:

Vaadin on the Web