From: Marko Gronroos
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 2 license (see license.html).
+ great, perform well and make you and your users happy. Vaadin and is
+ available under the Apache 2 license (see license.html).
- Vaadin is distributed as a single JAR file. Inside the JAR you will find:
+ Vaadin is distributed as a ZIP package and from the Maven central
+ repository. Without Maven, the recommended way to get Vaadin is to use the Vaadin
+ Plugin for Eclipse, which automatically downloads the Vaadin libraries.
Inside the ZIP installation package you will find:
+ See the README.TXT for information about the installation. Book of Vaadin (for Vaadin 7) will give more detailed
+ instructions at some point, but is not yet updated at the time of this release.
+
+ For server-side development, copy the vaadin-server,
+ vaadin-client-compiled, vaadin-shared, and
+ vaadin-themes-compiled from the main folder and the dependencies from the
+ lib folder to the WEB-INF/lib folder of your Vaadin project. The
+ vaadin-theme-compiler can be copied to a library folder that is not
+ deployed with the web application. (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 pure client-side development, you only need the vaadin-client and
+ vaadin-client-compiler JARs. 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.
+
@@ -76,7 +105,7 @@
for the purpose of receiving feedback about the changes.
The major changes in this first beta release are: The major new changes in this first beta release are:
@@ -108,7 +145,7 @@
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
- Root or Root.LegacyApplication instead of Application.
-
- 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.
+ 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 changed to use the new client-server
- communication API or the Vaadin 6 compatibility API.
+ Any custom client-side widgets need to be ported to use the new client-server
+ communication API, or the Vaadin 6 compatibility API.
- A detailed list of migration changes are given in the Vaadin 7 Migration
- Guide.
+ 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.
Release Notes for Vaadin Framework @version@
-
- Package Contents
+ Overview
Package Contents
+
+
-
+ Enhancements in Vaadin @version-minor@
-
+
+
+
+
@@ -164,24 +201,21 @@
Vaadin @version@ Dependencies
@@ -212,18 +246,14 @@
@@ -232,8 +262,8 @@
- Using the "?debug" URL parameter you can verify that the version of the servlet - (JAR), the theme and the widgetset all match. + By using the "?debug" URL parameter, you can verify that the version of + the servlet, the theme, and the widget set all match.
@@ -251,11 +281,12 @@
- Liferay and other portal users must install the new vaadin-@version@.jar as
-
Avoid using the session for storage, usual App Engine limitations apply (no - synchronization, i.e, unreliable). + synchronization, that is, unreliable).
DO NOT update application state when serving an ApplicationResource - (e.g ClassResource.getStream()). + (such as ClassResource.getStream()).
AVOID (or be very careful when) updating application state in a TransactionListener or a HttpServletRequestListener - they are - called even when the application is not locked and won't be serialized (e.g - ApplicationResource), and changes can thus go missing (it should be - safe to update things that can be safely discarded later - i.e valid only for - the current request) + called even when the application is not locked and won't be serialized (such + as ApplicationResource), and changes can thus go missing (it should be + safe to update things that can be safely discarded later, that is, those valid + only for the current request)
@@ -389,11 +420,11 @@@@ -402,8 +433,8 @@