Version 7.4.0 built on 2015-02-16.
Release Notes for Vaadin Framework 7.4.0
- Overview of Vaadin 7.4.0 Release
- Change Log for Vaadin 7.4.0
- Enhancements in Vaadin 7.4
- Incompatible or Behavior-altering Changes in 7.4
- Known Issues
- Limitations
- Vaadin Installation
- Package Contents
- Migrating from Vaadin 6
- Vaadin 7.4.0 dependencies
- Upgrading to Vaadin 7.4
- Supported Technologies
- Vaadin on the Web
Overview of Vaadin 7.4.0 Release
Vaadin 7.4.0 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
This release includes the following closed issues:
#2794 | Change IndexedContainer to use ItemAddedEvent and ItemRemovedEvent | |
Vote | #3087 | Add freeze columns support to Grid |
Vote | #3153 | Auxiliary headers for Grid |
#3171 | Grid should support partial updates | |
Vote | #5386 | Multiple sort columns for Grid |
Vote | #5542 | Support adding components to Grid header and footer |
#6847 | NativeSelect: support for focus and blur listeners | |
#6876 | TabSheet tab selection algorithm can be improved | |
Vote | #7225 | Enhancement: CellStyleGenerator for Grid footer and header |
#7262 | Grid should support a "select all" check box in the header | |
#7749 | declarative UI presentation API | |
Vote | #7850 | Rewrite Table to be modular and extensible |
#8787 | Multi selection in a grid should guarantee order | |
#8942 | Create a common wrapper for the two used JSON libraries | |
#9030 | Event captions should support HTML | |
#9045 | Optimize @JavaScript and @StyleSheet handling by including in html if possible | |
#9426 | Html Support for component Caption | |
Vote | #10672 | BeanFieldGroup should use Introspection to determine property types. |
Vote | #10975 | DefaultFieldGroupFieldFactory.createEnumField not working as expected |
#11038 | DefaultFieldGroupFieldFactory is not a singleton | |
#11433 | Possibility to use converters to format item captions in selection components | |
#12087 | DeploymentConfiguration should have dedicated methods for all init parameters used by Vaadin | |
#12210 | Load Push,Bootstrap script and themes with a version parameter | |
#12371 | FieldGroup.setDataSource() doesn't reset all previous Field values so ValueChangeListeners don't fire | |
#12453 | BeanFieldGroup is not able to buildAndBind a nested property by using three parameters | |
#12645 | Implement Escalator widget | |
#12733 | Make it possible to change URL of BrowserWindowOpener | |
#12829 | Implement base Grid component | |
#12830 | Grid column API | |
#12878 | Implement DataSource for Grid | |
#12882 | SQLContainer.removeAllItems() hangs while paging | |
#12907 | Support merging header/footer cells in Grid | |
#12936 | Polling do unnecessary layouting | |
#12993 | Cell Renderers for Grid | |
#13024 | Support changing column widths in Grid | |
#13058 | Support changing primary style names | |
#13062 | Grid should be com.vaadin.ui.Grid | |
#13065 | Grid should not be scrollable when disabled | |
Priority | #13180 | Modal window allows browser navigation via backspace |
#13327 | Implement programmatic scrolling for Grid | |
#13334 | Implement Grid | |
#13416 | AbstractSelectTargetDetails should implement getMouseEvent() | |
#13492 | Textfield value not updated when InputPromt and ShortcutListener are used | |
#13579 | Provide AbstractConnector constructor accepting and extending a conncetor | |
#13611 | Disallow eager layout while handling changes from the server | |
#13710 | Make setting viewport meta tag easy | |
#13775 | It should be possible to retrieve from a FieldGroup all fields that have failed validation | |
Vote | #13834 | Support generated properties in Containers |
Vote | #13883 | Do not hard code TransactionalPropertyWrapper |
#14227 | Call markAsDirty in AbstractComponentContainer when hierarchy changes | |
#14253 | Tomcat crashing when displaying Image created by null File | |
#14348 | NullPointerException in VTabSheet | |
#14460 | Add option to disable sending URLs as parameters | |
#14522 | Update to GWT 2.7 | |
#14534 | Upgrade to Atmosphere 2.2.3.vaadin2 and javascript 2.2.5.vaadin1 | |
#14583 | Add new StringTo<javadatatype>Converters to fully support all native Java data number types | |
#14584 | Add new RangeValidators to support more Java-native base types | |
#14594 | Elemental.json asserts if null system messages configured | |
#14609 | Allow HTML in TabSheet/Accordion tab captions | |
Priority | #14659 | BeanItemContainer.getType() returns wrong value for properties with primitive type |
#14666 | Compare Elemental JSON and org.json performance | |
#14670 | Make UI Class available in app class attribute | |
#14714 | Optimize client-side connector unregistering | |
#14731 | BeanFieldGroup.setItemDataSource(Item) does not accept null | |
Priority | #14742 | Problem on getting the message of the CommitException using Vaadin 7.2.7 |
Priority | #14748 | Pick annotation scanning fixes for the vaadin atmosphere fork |
#14755 | Add a clear() method to fields and field group | |
#14756 | Add StringToEnumConverter | |
#14845 | New project by NetBeans plugin contains SASS error: Unexpected token SASS_VAR found | |
#14881 | VPopupPanel does not compiles with gwt 2.7.0-SNPAHOT | |
#14904 | Show push version information in debug window | |
#14925 | Drop Opera 12 support | |
Priority | #15105 | vaadin-themes manifest exports unconventional package names for OSGI |
#15193 | ComboBox should use locale for filtering | |
#15210 | Support Android 5 | |
#15228 | Persist on-the-fly scss cache results | |
#15276 | Do not create String Writer where not needed | |
#15281 | Responsive does not work with setTheme | |
#15342 | DateField.setRangeStart fails if set to java.sql.Date | |
#15354 | Make AbstractFIeld.isEmpty public | |
#15363 | vaadin-archetype-application 7.3.6 mod request | |
#15373 | Allow handling loading indicator for ServerRPC in widget | |
#15375 | JSON version old | |
#15383 | Widgetset compilation fails if charts 2.x with 1.x license is included | |
#15408 | Window title does not use all available space. Gets truncated. | |
#15411 | Removing Grid header rows when scrolled causes a JS exception | |
#15414 | Atmosphere annotation processing takes a long time | |
#15417 | There is no Object to String converter | |
Priority | #15418 | Grid doesn't update row height when theme is changed on the fly |
#15422 | Grid resets scroll position on state change | |
#15427 | Disabled Grid should disallow interaction | |
#15430 | Don't log a warning message when not setting a renderer for strings (client side) | |
#15436 | Grid overlaps form in archetype | |
#15440 | Application example archetype should use @Viewport in 7.4 | |
#15443 | IndexOutOfBoundsException in RpcDataProviderExtension | |
#15447 | Add Table-compatible constructors to Grid | |
#15449 | Item double click support | |
#15452 | Super dev mode does not work | |
#15454 | Grid does not update correctly when rows are removed | |
#15465 | Grid shows only a small part of the data available | |
#15475 | Grid column shrink to fit occasionally broken on IE9 | |
#15476 | Adding rows to visible area of grid can cause issues | |
#15482 | getColumns returns a list of nulls after changing container in Grid | |
#15485 | Implement JavaScript renderer support | |
#15486 | Server-side cell style generator causes client-side exception if the selection checkbox column is visible | |
#15487 | Grid headers and footers create unnecessary cells | |
#15488 | Client-side exception thrown if selecting rows in Grid during initial rendering | |
#15508 | JsonCodec with elemental broken | |
#15510 | Client side grid has an odd import for GridColumnState | |
#15511 | Client side Grid speaks of header texts, not captions | |
#15512 | Server side Grid column getColumnProperty makes no sense | |
#15534 | SerializerTest.testSerialization() is not deterministic | |
#15536 | Invalid input in editor breaks editing in Grid | |
#15544 | Build a vaadin-widgets module | |
#15545 | Validate and fix declarative support for AbstractSelect | |
#15546 | Validate and fix declarative support for ComboBox | |
#15547 | Validate and fix declarative support for ListSelect | |
#15548 | Validate and fix declarative support for NativeSelect | |
#15553 | Grid/Escalator can not depend on Util | |
#15555 | Profiler should not depend on debug window classes | |
#15556 | No error handling in Grid Editor | |
#15558 | elemental.json.Json included in both vaadin-server.jar and vaadin-shared.jar | |
#15560 | Support JsonValue and subclasses in state and rpc | |
#15561 | Cache reference diffstate values | |
#16173 | many animated ProgressBars look annoying with animated background | |
#16187 | Grid's header deco element isn't recalculated appropriately | |
#16189 | Grid scrollToRow on init doesn't work. | |
#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. | |
#16199 | Grid.cancelEditor() does not discard changes | |
#16200 | Widgets in Grid cells are aligned poorly | |
#16202 | ProgressBarRenderer widgets should be 100% wide | |
#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 | |
#16313 | Validate and fix declarative support for DateField | |
#16314 | Validate and fix declarative support for PopupDateField | |
#16315 | Validate and fix declarative support for InlineDateField | |
#16316 | Validate and fix declarative support for ProgressBar | |
#16317 | Validate and fix declarative support for Tree | |
#16320 | Column can be set sortable even if container is not. | |
#16322 | Validate and fix declarative support for Link | |
#16323 | Validate and fix declarative support for Upload | |
#16326 | Validate and fix declarative support for RichTextArea | |
#16333 | Validate and fix declarative support for TwinColSelect | |
#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 | |
#16474 | Grid performance with lots of columns | |
#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 | |
#16505 | Grid not visible in tab sheet fails on several operations | |
#16509 | Editor row CommitException should not be set as component error | |
#16512 | Grid.getEditorFieldFactory is missing | |
#16513 | Editor row field factory should only create inline fields | |
#16515 | It should be possible to easily handle commit errors in Grid editor | |
#16521 | Client vs. server renderer package naming is inconsistent | |
#16522 | Infinite loop in reading a design where a tag ends in a dash | |
#16525 | Checkboxes are incorrectly aligned in Grid editor | |
#16528 | Add ValoTheme.UI_WITH_MENU to archetype UI's | |
#16532 | Grid uses wrong color variable for selected row color (Valo) | |
#16533 | Grid column widths are wrong in IE10 and IE11 | |
#16534 | Grid editor save/cancel buttons can be hidden underneath the footer | |
#16538 | It should be possible to decide which Grid columns are not editable | |
#16542 | Don't require DataSource implementors to implement indexOf | |
#16551 | Make it possible to change caption of grid editor save and cancel buttons | |
#16554 | Update framework to use Sass compiler 0.9.12 | |
#16562 | Grid Editor's save/cancel buttons should always be in view | |
#16567 | Unselecting a row in Grid is impossible | |
#16572 | DesignAttributeHandler cache is never used | |
#16575 | Grid Editor errors should be highlighted on a cell level | |
#16581 | Server unit tests fail when run in Eclipse | |
#16582 | Use non-blocking map for global Declarative caches | |
#16591 | Grid: mousewheel does not work in Safari when using webcomponents polyfill | |
#16593 | Grid editor theme redesign | |
#16599 | WidgetUtil.getRequired[Width|Height]BoundingClientRectDouble methods round up the return value | |
#16602 | Show commit error message from Grid editor to the user | |
#16606 | Grid calculates row widths wrong in Firefox | |
#16634 | Can't scroll in IE8-IE11 using scroll bar arrows | |
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.
- The vaadin-widgets JAR package containing only GWT Widgets intended for standalone use without the rest of the framework. Currently only contains Grid.
- 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)
- Widgets for standalone client-side use (vaadin-widgets)
- 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.)
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.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.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 supports the following desktop browsers:
- Mozilla Firefox 18-35
- Mozilla Firefox 17 ESR, 24 ESR, 31 ESR
- Internet Explorer 8-11
- Safari 6-8
- Opera 16-27
- Google Chrome 23-40
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