From d776fcff8caf5c39b809b9fd6d38af5442864b21 Mon Sep 17 00:00:00 2001
From: Henri Sara
Date: Fri, 18 Dec 2009 09:23:54 +0000
Subject: [PATCH] Minor corrections to release notes
svn changeset:10419/svn branch:6.2
---
WebContent/release-notes.html | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/WebContent/release-notes.html b/WebContent/release-notes.html
index 0672acaf21..a0d5bf20b3 100644
--- a/WebContent/release-notes.html
+++ b/WebContent/release-notes.html
@@ -45,7 +45,7 @@ contains a number of significant enhancements.
A widget set definition class is no longer used. Java code needed for widget
instantiation and client-server mapping is automatically generated by GWT
- compiler. For common Vaadin user, Widgetset is now only a GWT module definition
+ compiler. For a common Vaadin user, Widgetset is now only a GWT module definition
file (.gwt.xml).
Server-side component is mapped to a client-side widget with an annotation:
@@ -71,10 +71,10 @@ public class ColorPicker extends AbstractField {
- On the server-side:
- - Listeners are now easier to implement with ReflectTools.findMethod()
- and addListener(String eventIdentifier, Class<?>
- eventType, Object target, Method method) methods. The latter
- automatically inform the client-side that a listener is registered on server side)
+ - Listeners for custom client side events are now easier to implement with
+ ReflectTools.findMethod() and addListener(String eventIdentifier,
+ Class<?> eventType, Object target, Method method) methods. The latter
+ automatically informs the client-side that a listener is registered on server side)
- On the client-side:
@@ -118,13 +118,13 @@ public class ColorPicker extends AbstractField {
- Additional Maven archetypes
- - vaadin-archetype-clean with dependency to Vaadin and a minimal application skeleton, no client side widgets
+ - vaadin-archetype-clean with a dependency to Vaadin and a minimal application skeleton, no client side widgets
- vaadin-archetype-widget for creation of Vaadin 6.2 widget packages
- vaadin-archetype-sample has been updated for Vaadin 6.2 - use version 1.0.x for earlier Vaadin versions
- Maven Vaadin plugin
- - vaadin-maven-plugin can automatically update Vaadin 6.2 widgetsets based on Maven dependencies using the goal update-widgetset
+ - vaadin-maven-plugin can automatically update Vaadin 6.2 widgetsets based on Maven dependencies using the goal update-widgetset
- HttpServletRequestListener
@@ -199,7 +199,7 @@ If you package a widget set as a JAR for use in other projects:
- Install new GWT JARs if the GWT version has changed
- - The Eclipse plugin will download the new GWT automatically when you update the Vaadin version; you will need to update GWT paths in the widget set compilation launch configurations in Eclipse (#3286).
+
- The Eclipse plugin will automatically download the new GWT and update launch configurations and the project build path when you update the Vaadin version.
- If you have custom widget sets, recompile them with the new Vaadin library using the included GWT compiler
- If using the Eclipse IDE:
@@ -311,10 +311,10 @@ under the Google App Engine.
DO NOT update application state when serving an ApplicationResource (e.g ClassResource.getStream()).
AVOID (or be very careful when) updating application state in a
- TransactionListener - it is 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)
+ 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)
The application remains locked during uploads - a progress bar is not possible
--
2.39.5