adin-client-compiler.7.6.1.source-code.release-notes.html Maven / Gradle / Ivy
Show all versions of vaadin-client-compiler Show documentation
Vaadin Framework 7.6.1
Vaadin – thinking of U and I
Version 7.6.1
Version 7.6.1 built on 2016-01-12.
Release Notes for Vaadin Framework
7.6.1
- Overview of Vaadin
7.6.1 Release
- Change Log for Vaadin
7.6.1
- Enhancements in Vaadin
7.6
- Incompatible or Behavior-altering Changes in
7.6
- Known Issues and Limitations
- Vaadin Installation
- Package Contents
- Migrating from Vaadin 6
- Vaadin 7.6.1
dependencies
- Upgrading to Vaadin
7.6
- Supported
Technologies
- Vaadin on the Web
Overview of Vaadin 7.6.1 Release
Vaadin 7.6.1 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.6.1
This release includes the following closed issues:
Priority #16842 Pressing Enter should save edited row in Grid #18525 ConnectorHierarchyChangeEvent.getParent() always returns null #18685 GeneratedPropertyContainer might throw NPE on item add #19064 StatementHelper SQLException does not report field correctly Priority #19086 Changing Grid renderers on fly uses wrong widget #19107 "Unsupported attribute" log when using declarative <v-link> Priority #19149 Uncaught client exception when new value is entered in ComboBox and newItemsAllowed is false #19209 HeaderCell ignore style #19347 Grid's visible columns selector not working after column resize has been added Priority #19392 Keyboard shortcuts are lost when focus is on body element #19409 Widgets in Grid header cause incorrect resize hande position and inoperable column reordering #19412 Debug window complains of unknown component connector in Grid #19421 Extra scrollbar in empty Grid in multiselect mode #19424 Component size not properly set to 100% in CSS Layout #19425 GeneratedPropertyContainer.getItem() returns an Item for a non-existing item id #19426 GeneratedPropertyContainer.getItem returns items which are not equal #19429 "Unsupported attribute" logged when reading Slider/AbstractEmbedded #19434 Label.writeDesign() does not handle null values correctly #19440 Grid does no support editor Fields with AbstractComponentConnector 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.6
Vaadin 7.6 includes many major and minor
enhancements. Below is a list of the most notable changes:
- New configurable client-server automatic reconnect handling and warning dialogs
- Grid columns can be resized by the user
- Grid non-modal editor mode and unbuffered datasource binding
- More fluent Grid scrolling for touch devices
- Better customizability of Grid (data generators for communication, customizable selection models etc.)
- Configurable keyboard, touch and mouse navigation support for Grid editor
- Declarative HTML serialization enhancements for Vaadin Designer 1.0
- Better handling of closing a window with keyboard shortcuts
- Column collapsing events for Table
- Most Components fire a ContextClickEvent when the user tries to open a context menu.
This event is specialised to contain some extra context for Grid, Table, TreeTable and Tree,
and used by the ContextMenu add-on.
- New push transport mode WEBSOCKET_XHR (WebSockets from server to client, XHR from client to
server) which allows setting of cookies, using request scopes with CDI/Spring etc.
- Navigator is more extensible and can be used with dependency injection
- It is possible to customize the push URL using PushConfiguration.setPushUrl().
This enables implementing some push related add-ons such as push on portals.
For enhancements introduced in Vaadin 7.5, see the Release
Notes for Vaadin 7.5.0.
Incompatible or Behavior-altering Changes in 7.6
- Window.setCloseShortcut() is now deprecated. ESCAPE is no longer a hard-coded default, but rather a soft one, and
can be removed. If the close-shortcut attribute of the v-windowelement is present, it must list all close
shortcuts, including ESCAPE, separated by whitespace. Existing, unchanged code should behave as before.
See ticket #17383 for more information on the reasoning
behind the change.
- Grid SelectionModels are now Extensions. This update removes all selection related variables and API from
GridConnector, GridState, GridServerRpc and GridClientRpc
- StringToEnumConverter now explicitly supports Enum types with custom toString() implementations.
This may affect applications that relied on the undefined behavior in previous versions.
- The Section enumeration from client-side of the Grid has been moved to GridConstants
- The order in which AttachEvents are fired has been changed. When attaching a component with child components,
events are now fired first for the children and last for the root component. The order is thus the same as
the order in which custom code in overridden Component.attach methods would be executed. Please refer to
ticket #16348 for more information on this change.
- Jsoup library version 1.8.3 is incompatible with the version 1.8.1 used in early 7.6 alphas and 7.5. This might
cause problems with external libraries compiled against said versions.
- Declarative format is now using "vaadin-" as a default prefix instead of the "v-" prefix used in 7.5.
This default can be changed in deployment configuration.
Known Issues and Limitations
- Vaadin TouchKit versions prior to 4.1.0 do not work with 7.6. Please use version 4.1.0 or above.
- Context click events are not generated on iOS devices
(#19367)
- 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 configuration needed for push and compatibility issues are available in
this wiki page.
The most prominent limitations are:
- Google App Engine has some limitations. Please consult Vaadin Wiki:
Vaadin support for Google App Engine
- Grid does not support adding components to cells. Instead light-weight Renderers can be
used to present and edit data.
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:
- Maven dependency.If using Maven, define it as a dependency or use
any of the available archetypes to create a new project. More information at
https://vaadin.com/maven
- IDE Plugins.If using Eclipse, use the
Vaadin Plugin for Eclipse, which automatically
downloads the Vaadin libraries. For NetBeans 8.0 and 7.4, use the
official Vaadin plugin
that provides Maven based wizards and code completion support for Vaadin development.
Vaadin Framework 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.6.1 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.6
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.
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-9
- 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.6.1 supports the following desktop browsers:
- Mozilla Firefox 18-43
- Mozilla Firefox 17 ESR, 24 ESR, 31 ESR, 38 ESR
- Internet Explorer 8-11, Edge
- Safari 6-8
- Opera 16-34
- Google Chrome 23-47
Additionally, Vaadin supports the built-in browsers in the
following mobile operating systems:
- iOS 5-9
- 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