Version @version@ built on @builddate@.

Release Notes for Vaadin Framework @version@

Package Contents

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 2 license (see license.html).

Vaadin is distributed as a single JAR file. Inside the JAR you will find:

=======
  • #8932: Custom build from 6.8
  • #8193: Enter ClickShortcut not working in a PopupView
  • #8584: Invalid behavior of multiselection for com.vaadin.ui.Table
  • #9136: Tree throws wrong ItemClickEvent in IE9 (when immediate is set to true)
  • #9139: TextArea in Internet Explorer
  • #9188: Error parsing maps with empty string as the last value
  • #7036: Enable scrollbars on a read-only RichTextArea
  • #8109: Iterating over Table multiselection causes multiple Vaadin SQLContainer full table scans
  • #8144: Can't use LoginForm inside an iframe
  • #9202: Test using Chrome 21
  • #6219: PDF viewer draws itself over floating Vaadin elements
  • #8230: TextField's input prompt is persisted if Alt is depressed while in focus (Chrome)
  • #8399: On IE 8 or Google Chrome 16, VOverlay components aren't display on top of Applet
  • #9148: Oracle TIMESTAMP not supported in SQLContainer
  • #9189: Variables sent to the DragAndDropManager are not logged in the debug console
  • #9128: Typo in vaadin book
  • #8736: com.vaadin.ui.Table component return null value on multiple selection
  • #9132: No entries in Table with a defined pageLength causes Table to shrink in height
  • #9147: SQLContainer Filters - Comparison against NULL value produces error
  • #9154: NumberFormatException in client-side component VSplitPanel
  • #9171: StreamVariable never cleaned up in CommunicationManager
  • #9187: No horizontal scroll bar on empty Table
  • #8838: Drag and Drop in Google Chrome causes ArrayIndexOutOfBoundsException in AbstractCommunicationManager#convertMap (1612)
  • #8917: input prompt text is leaking into the component's value

    • The full list of the closed issues can be found at dev.vaadin.com.

    >>>>>>> remotes/origin/6.8

    Enhancements in Vaadin @version-minor@

    @version-minor@ is the third development release of the upcoming Version 7 of the Vaadin Framework. It introduces the third set of new features in Vaadin 7, for the purpose of receiving feedback about the changes.

    The major changes in this third alpha phase are:

    The enhancements are described in more detail in the mini-tutorials in the Vaadin Wiki.

    Please see the release notes for alpha1 and alpha2 for a complete list of major enhancements for Vaadin 7 so far.

    ChangeLog

    For a complete list of changes in this release, please see the list of closed tickets.

    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 Root or Root.LegacyApplication instead of Application.

    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.

    Any custom client-side widgets need to be changed to use the new client-server communication API or the Vaadin 6 compatibility API.

    A detailed list of migration changes are given in the Vaadin 7 Migration Guide.

    Vaadin @version@ Dependencies

    Bean Validation

    If you want to use the bean validation feature in Vaadin 7, you need a Bean Validation API implementation. You need to install the JAR in the WEB-INF/lib directory.

    Upgrading to Vaadin @version-minor@

    Upgrading the Eclipse Plugin

    This release requires that you use the experimental Vaadin Plugin for Eclipse. Its update site is http://vaadin.com/eclipse/experimental. Please see the installation instructions for more details.

    General Upgrading Instructions

    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.

    Using the "?debug" URL parameter you can verify that the version of the servlet (JAR), the theme and the widgetset 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 new vaadin-@version@.jar as ROOT/WEB-INF/lib/vaadin.jar in the portal. Additionally the contents of the VAADIN folder from the JAR must be extracted to the ROOT/html/VAADIN directory in the Liferay installation. If your portal uses custom widgets, install the latest version of Vaadin Control Panel for Liferay 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 it is also compatible with most other operating system supporting Java 6 or newer.

    Vaadin 7 is 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. All portals that implement either of the portlet specifications should work. The following portals are supported:

    Vaadin also supports Google App Engine.

    Vaadin supports the following desktop browsers:

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

    Vaadin on the Web