Version 7.4.0.beta3 built on 2015-01-30.
Release Notes for Vaadin Framework 7.4.0.beta3
- Overview of Vaadin 7.4.0.beta3 Release
- Change log for Vaadin 7.4.0.beta3
- Enhancements in Vaadin 7.4
- Incompatible or behavior-altering changes in 7.4
- Known issues in 7.4
- Limitations in 7.4
- Vaadin Installation
- Package Contents
- Migrating from Vaadin 6 to Vaadin 7
- Vaadin 7.4.0.beta3 dependencies
- Upgrading to Vaadin 7.4
- Supported technologies
- Vaadin on the Web
Overview of Vaadin 7.4.0.beta3 Release
Vaadin 7.4.0.beta3 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.4.0.beta3
This release includes the following closed issues:
| #13416 | AbstractSelectTargetDetails should implement getMouseEvent() | |
| #13611 | Disallow eager layout while handling changes from the server | |
| #15363 | vaadin-archetype-application 7.3.6 mod request | |
| #15408 | Window title does not use all available space. Gets truncated. | |
| #15411 | Removing Grid header rows when scrolled causes a JS exception | |
| Priority | #15418 | Grid doesn't update row height when theme is changed on the fly |
| #15436 | Grid overlaps form in archetype | |
| #15440 | Application example archetype should use @Viewport in 7.4 | |
| #15449 | Item double click support | |
| #15508 | JsonCodec with elemental broken | |
| #15556 | No error handling in Grid Editor | |
| #16173 | many animated ProgressBars look annoying with animated background | |
| #16191 | HeightMode.ROW in Grid does not always apply correctly | |
| #16192 | Sorting grid with not used properties leads to client side exception | |
| #16194 | Grid's sort event user origin wasn't always used. | |
| #16200 | Widgets in Grid cells are aligned poorly | |
| #16214 | Opening Grid editor for row not visible causes exception in IE8 | |
| #16217 | Widgets module depends on server/client/shared/compiler | |
| #16219 | Grid does not tell you if you try to remove a non-existing column | |
| #16244 | Make Grid data RPC send the value as Json instead of encoding it as a string | |
| #16259 | Grid selection method javadocs and exception messages are needlessly technical | |
| #16260 | ButtonRenderer button doesnt' have v-button style in Grid | |
| #16262 | Client Grid.addColumn should return the exact column type given as a parameter | |
| #16273 | Window caption is HTML although captionAsHtml is false | |
| #16275 | Sorting multiple Grid columns with Shift key selects captions | |
| #16311 | Grid throws an exception if using a Container not implementing Container.Sortable | |
| #16320 | Column can be set sortable even if container is not. | |
| #16341 | Touch scrolling on Grid feels choppy on iOS | |
| #16388 | Rename archetype-application to archetype-application-multimodule | |
| #16397 | missing select all checkbox | |
| #16433 | Grid produces incorrect human readable headers for nested properties | |
| #16481 | Grid RpcDataProviderExtension fails with sorting | |
| #16483 | Grid allows non sortable properties column to be sortable | |
| Priority | #16490 | Broken OSGI dependencies in vaadin-server |
| #16502 | Grid Editor scroll lock resets with setEnabled | |
| #16522 | Infinite loop in reading a design where a tag ends in a dash | |
| #16528 | Add ValoTheme.UI_WITH_MENU to archetype UI's | |
| 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.4
The 7.4 includes many major and minor enhancements. Below is a list of the most notable changes:
- Grid is a new component for showing tabular data. It has been
designed from the ground up to eventually replace the Table
and TreeTable components.
The most notable Grid features in 7.4 are:- Support for multiple rows in the header and footer sections.
- Renderer concept for customizing how the data in a given column is represented in the browser.
- Support for frozen columns.
- Support for inline editing of one row at a time.
- Support for components in header and footer cells.
- Hardware accelerated, touch optimized scrolling.
- Declarative layout support for initializing a component hierarchy from an HTML file.
- Uses GWT 2.7 for improved compilation times when using Super Dev Mode.
- @Viewport annotation for declaratively defining a mobile viewport definition for a UI.
- Component captions, TabSheet/Accordion tab captions and Calendar event captions can be configured to be displayed as HTML.
- Selects use converters when presenting itemids.
- Improved performance when server response contains no visual changes (e.g. empty polling responses).
- Development time on-the-fly scss compilation cache may now be preserved when redeploying or restarting the server.
- Unified JSON library for using the same API in both server-side and client-side code.
- Range validators and converters for additional numerical types.
- Support for fine grained add/remove item events in in-memory containers.
For enhancements introduced in Vaadin 7.3, see the Release Notes for Vaadin 7.3.0.
Incompatible or behavior-altering changes in 7.4
-
The org.json and com.google.gwt.json libraries have been replaced by elemental.json.
JavascriptFunction.call parameter type has been changed to elemental.json.JsonArray, affecting JavaScript.addFunction, AbstractJavaScriptComponent.addFunction and AbstractJavaScriptExtension.addFunction
Raw JSON values passed to AbstractJavaScriptComponent.callFunction and AbstractJavaScriptExtension.callFunction should be changed to use elemental.json types.
- The semantics of empty and required for Field classes has been made more consistent. This mainly affects Checkbox which is now considered to be empty when it is not checked.
- The previously inconsistent behavior in HTML vs plain text rendering of Calendar event captions has been made consistent.
- Support for Opera 12 has been dropped. Newer versions based on the Blink rendering engine are still supported.
Known issues
- Drag'n'drop in a Table doesn't work on touch devices running Internet Explorer (Windows Phone, Surface) (#13737)
Limitations
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.
- Push is currently not supported in portals (See #11493)
- HTTP session can not be invalidated while using push over websockets on Tomcat 7 (#11721)
- Cookies are not available while using websockets (#11808)
- Not all proxies are compatible with websockets or streaming. Use long polling to avoid these problems.
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:
- If using Maven, define it as a dependency or use any of the available archetypes (only vaadin-application is available for Vaadin 7 at the time of this release) to create a new project
- If using Eclipse, use the Vaadin Plugin for Eclipse, which automatically downloads the Vaadin libraries.
It 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.4.0.beta3 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 from Vaadin 7.1 to Vaadin 7.4
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
Notes and Limitations for Google App Engine
The following instructions and limitations apply when you run a Vaadin application under the Google App Engine.
-
Applications must use GAEVaadinServlet instead of VaadinServlet in web.xml .
-
Session support must be enabled in appengine-web.xml :
<sessions-enabled>true</sessions-enabled>
-
Avoid using the session for storage, usual App Engine limitations apply (no synchronization, that is, unreliable).
-
Vaadin uses memcache for mutex, the key is of the form _vmutex<sessionid> .
-
The Vaadin VaadinSession class is serialized separately into memcache and datastore; the memcache key is _vac<sessionid> and the datastore entity kind is _vac with identifiers of the type _vac<sessionid> .
-
DO NOT update application state when serving an ConnectorResource (such as ClassResource.getStream()).
-
The application remains locked during uploads - a progress bar is not possible
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:
- 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
- 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.4.0.beta3 supports the following desktop browsers:
- Mozilla Firefox 18-34
- Mozilla Firefox 17 ESR, 24 ESR, 31 ESR
- Internet Explorer 8-11
- Safari 6-8
- Opera 16-27
- Google Chrome 23-39
Additionally, Vaadin supports the built-in browsers in the following mobile operating systems:
- iOS 5-8
- 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