adin-client.7.4.3.source-code.release-notes.html Maven / Gradle / Ivy
Show all versions of vaadin-client Show documentation
Vaadin Framework 7.4.3
Vaadin – thinking of U and I
Version 7.4.3
Version 7.4.3 built on 2015-03-31.
Release Notes for Vaadin Framework
7.4.3
- Overview of Vaadin
7.4.3 Release
- Change Log for Vaadin
7.4.3
- Enhancements in Vaadin
7.4
- Incompatible or Behavior-altering Changes in
7.4
- Known Issues and Limitations
- Vaadin Installation
- Package Contents
- Migrating from Vaadin 6
- Vaadin 7.4.3
dependencies
- Upgrading to Vaadin
7.4
- Supported
Technologies
- Vaadin on the Web
Overview of Vaadin 7.4.3 Release
Vaadin 7.4.3 is a maintenance release that includes a
number of new bug fixes, as listed in the change log below.
Change Log for Vaadin 7.4.3
This release includes the following closed issues:
Priority #14796 Table column header sorting stops working on Chrome #14864 Text fields and areas don't get focus on some WP devices Priority #15220 Incorrect logging when a push connection does not find a session Priority #15294 IE + IFrame + Table scrolls up when selecting a row Priority #16552 Column.setRenderer has no effect #17025 Create a Maven BOM for Vaadin #17091 Grid in SelectionMode.MULTI doesn't use full width at all Priority #17132 Grid Multiselect: Editmodus allows invalid selection #17204 Declarative does not support primitive float and double properties #17205 Declarative support for BigDecimal properties is broken #17222 "This should not happen" sever message logged on each refresh in Firefox/Chrome when using websockets #17235 Allow overriding UIConnector.replaceTheme() and UIConnector.activateTheme() Priority #17248 Remove component from accordion cause client side exception #17300 Use vaadin-parent POM in framework POMs 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
Vaadin 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 and Limitations
- Drag'n'drop in a Table doesn't work on touch devices running
Internet Explorer (Windows Phone, Surface)
(#13737)
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.
- Up-to-date information about compatibility issues with push functionality is available in
this wiki page.
The most prominent limitations are:
- HTTP proxies can prevent push requests from working
properly. To mitigate the issues, avoid using streaming
and configure your proxy so it allows response headers
to pass through before the whole response is received.
#17075
should make long-polling work seamlessly with all proxies.
- HTTP session can not be invalidated while using
push over websockets on Tomcat 7 (#11721)
- Cookies are not available while using websockets (#11808)
- Push is currently not supported in portals (See #11493)
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.3 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
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.
-
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.3 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