Version 7.3.0 built on 2014-09-01.

Release Notes for Vaadin Framework 7.3.0

Overview of Vaadin 7.3.0 Release

Vaadin 7.3.0 is a minor 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.3.0

This release includes the following closed issues:

#2874Add support for changing theme on the fly without reloading
#9303Implement VOverlay shadow with CSS box-shadow when possible
#9532On the fly Scss compiler could cache result
Priority#13432Polling disturbs user interaction on table column resize
Priority#13444ComboBox computed width breaks on stylename change
#13546Provide methods for setting only width or height undefined.
#13563Debug window styles should not be included in the base theme
Priority#13565client.isActive() does not work consistently with Table when testing with QFTest/Testbench
#13616Use GWT as a dependency in the project
#13618Import theme Valo to Vaadin
#13634Theme JAR has extra test folders
#13643setChildrenAllowed false has no effect in Valo theme
#13660Implement Notification animations using CSS instead of JavaScript
#13661Deprecate VOverlay shadow API
#13668Review current Sass API for Valo
#13670Rename v-app-background-color to v-background-color in Valo
#13671Vertical alignment in auto height HorizonlLayout is broken in Valo
#13672Notification styles should be parametrized in the Valo build
#13674Implement DragAndDropWrapper styles for Valo
#13677Panel does not calculate size correctly in Valo theme
#13680Add default styles for anchor elements in Valo
#13686Remove 'v-' prefix from all Valo mixins and functions
#13722VCalendarPanel throws NPE when DateField's time format is changed from 24h to 12h and popup calendar is opened
#13746(Valo) DragAndDropWrapper styles should not hide the drag target element
#13806Add a helper for retrieving the current PortletRequest
Priority#13812OSGi manifest for vaadin-shared is wrong
#13836DragAndDropWrapper does not support choosing a custom component as the drag image
Priority#13885Subwindow title area calculations get messed up after maximize/restore
#13944Change back to org.json
#13990Notification position should be controllable with CSS
#14009OSGi - Vaadin server requires wrong theme compiler bundle
#14030Add Java constants for all additional Valo theme style names
#14031Create automated TB tests for all views in ValoThemeTest app
#14051Super Dev Mode generates incorrect source maps when using
#14055Remove VWindowOverlay
#14058Valo causes Table headers to be overly long
Priority#14059@DelegateToWidget does not work for widget descendants with overridden getState
#14072Browser details are re-sent in the first UIDL request
#14081Confusing error in logs when server sends a critical notification
#14082Remove unused VaadinServlet.handleServiceSecurityException method
#14084Allow ignoring the sync id functionality
#14093Add -webkit prefix for box-shadows in Valo
#14105Update release notes
#14106Update licenses file
#14107Document remaining additional style names for Valo
#14112Empty rows in Table are badly styles
#14120Compile valo with Vaadin Sass compiler
#14124Embedded applications get no theme class name (regression by #2874)
#14139Problem with setTheme method for Overlay components.
#14142Vaadin 7.3 : Optimize AbstractClientConnector.getAllComponentsIterable()
#14145Fix background color for chameleon theme
#14152VerticalSplitPanel inside a HorizontalSplitPanel doesn't display its second component (Valo theme)
#14162There is unnecessary shadow in menu in runo theme.
#14167Update release notes
#14172Fix regression caused by #13885 for notification in chameleon.
#14173Fix box shadow bug with resizing elements in IE9 and IE10.
#14195Combobox popup has extra shadow when resized.
#14200Error i Valo-demo; Combo Box
#14219Rich text area has broken icons in Valo theme
#14225TexArea 'white-space: normal' breaks multiline texts in Valo
#14232Add assertions for container size not being negative
#14238Immediate upload with Valo is broken
#14246Fix background color of Notification in chameleon theme in IE8
#14284Add a constant for vaadinBootstrap.js similar to vaadinPush.js
#14303Merge fixes from master
Priority#14304TabSheet focus events don't work as intended on different browsers.
#14330Ensure there are no empty @since tags
#14331Base theme sets system notifications to 70% opacity
#14334Valo Tree selection indicator broken in Blink (Chrome 36 and Opera 23, OS X)
#14336Inconsistent font rendering for Open Sans on Windows
#14338Valo reports theme version wrong in debug window
#14343Drag and drop wrapper does not properly work with Valo
#14351valo theme with drag and drop upload
#14352Increase TB3 socket timeout
#14354ResponsiveConnector should request layout update when breakpoints change
#14360Valo Tree Drag & Drop styles broken
#14361GridLayout.space() not working
#14364Ensure license checker works for different license types
#14368Notification delay is not set to 0 when the notification is clicked
#14374Split common-stylenames to individual component files
#14376On Windows Phone 8.1 Update, IE11 is identified as Safari
#14379Opening a combobox with keyboard input and pressing enter to select an item does not close the popup.
#14392GridLayout does not position items in columns correctly
#14396Update Font Awesome to latest version
#14401Table column resize does not work in Valo (Firefox)
#14408Allow specifying license for multiple major versions
#14412Slider broken on initial render in IE8 (Valo)
#14413Window close and maximize/restore buttons not visible on initial render in IE8 (Valo)
#14446Testbench loses screenshots
#14447Error notification closes without user input on touch devices
Priority#14475Vaadin Table Scroll To Row Issue
 
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.3

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

Incompatible or behavior-altering changes in 7.3

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

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

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