Version 6.6.0 built on 2011-05-09.

Release Notes for Vaadin Framework 6.6.0

Vaadin 6.6.0 is an update release for Vaadin Framework 6. In addition to various fixes, it contains a number of significant enhancements.


General enhancements:

In the server-side API:

In the client-side API:

Backward-Incompatible Changes

Change Log, Future Releases, and Upgrading

See the following lists of closed tickets for a complete list of changes in this release:

Problem fixes and enhancements planned for upcoming releases can be found in the Vaadin Roadmap in Vaadin Trac.

As always, when upgrading from an earlier version, you should recompile any custom widget sets and refresh your project in Eclipse. If you are upgrading from 6.5.x or earlier, notice that Vaadin 6.6 uses GWT 2.3 (included in the installation package). See General Upgrade Instructions for more details on upgrading.

Upgrading from Vaadin 6.0 or 6.1

The way how widget sets are defined was simplified in Vaadin 6.2. Existing projects, where custom widgets (a custom widget set) are used, must be migrated when upgrading to Vaadin 6.2 or later. Projects where the default widget set is used do not need migration. For most projects this should be a quite painless upgrade.

For applications where custom widgets are used (also applicable to widget projects):

If you are using widgets from another project (typically in a separate JAR file):

If you package a widget set as a JAR for use in other projects:

General Upgrade Instructions

When upgrading from an earlier version of the Vaadin library, you should always do the following.

All Users

Eclipse Users

  1. Upgrade the Vaadin Integration Plugin for Eclipse to the latest version
  2. Set your project to use the new Vaadin version
    1. Select the new version in the Vaadin section in project preferences1
    2. The Eclipse plugin will automatically download the required GWT libraries and update launch configurations and the project build path
  3. If you have installed Vaadin add-ons containing custom widget sets, recompile them by selecting the project or the widget set and clicking the Compile Vaadin widgets button in Eclipse toolbar
  4. Stop the development server, clean up the working directories, and restart the server.

1 The Vaadin section is enabled only if the Vaadin Facet is configured for the project

NetBeans and Build Script Users

If you build the Vaadin application or the widget sets using an Ant script, such as in NetBeans, follow the following instructions:

  1. Copy the vaadin-6.6.0.jar library to the WEB-INF/lib directory in the project and remove the old version
  2. Refresh the project (in NetBeans or Eclipse)
  3. If using any add-ons containing custom widget sets:
    1. If the GWT version has changed, copy the GWT libraries to the compilation-time library directory of the project. The GWT libraries should not be located in the WEB-INF/lib directory, as they are not deployed together with the web application.
      • gwt-user.jar
      • gwt-dev.jar
      • validation-api-1.0.0.GA.jar (a GWT dependency)
      • validation-api-1.0.0.GA-sources.jar (a GWT dependency)
    2. The build script must include all the mentioned libraries in its class path
    3. Recompile the widget set using the build script

You can use the WebContent/docs/example-source/build-widgetset.xml Ant script in the Vaadin installation package as a template for a script for compiling the widget sets.

Maven Users

Maven downloads the defined Vaadin version and required GWT libraries automatically.

Notice that there can sometimes be a delay between the official release of Vaadin to when it is submitted to the central repository. Once in the central repository, the replication to other repositories can take several hours.

Liferay Users

  1. You may need to install a new version of the Vaadin Control Panel for Liferay
  2. Install the new Vaadin Jar to the ROOT/WEB-INF/lib directory in the portal
  3. Extract the contents of the VAADIN folder from the Jar to the static ROOT/html/VAADIN directory in Liferay. Only the PortalDefaultWidgetSet widget set is needed.
  4. If using any add-on components or custom widget sets, use the Vaadin Control Panel to recompile the combining widget set

Similar instructions apply for other portals, except that you need to recompile the widget sets for example using the build-widgetset.xml script included in the Vaadin installation package.

Notes and Limitations for Google App Engine

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

Important known problems in Vaadin 6.6.0

For other known problems, see open tickets at developer site


Vaadin is available for the following operating systems:

Vaadin supports Java Servlet API 2.3 and later versions and should work with any Java application server that conforms to the standard. It supports the following application servers:

Vaadin supports the following browsers for using the applications made with it:

The support for browsers follows the support by GWT. The browsers are supported on both Windows and Mac, if available. Firefox is supported also on Linux. There may be differences between the exact versions of the supported browsers that may cause incompatibility with applications made with Vaadin.