From: Artur Signell
Date: Fri, 18 Dec 2009 09:12:28 +0000 (+0000)
Subject: Rewrote the upgrade information and added
X-Git-Tag: 6.7.0.beta1~2105
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=95dc98c5d0e00b6805b590cfda5e0b9200eaea24;p=vaadin-framework.git
Rewrote the upgrade information and added
HttpServletRequestListener+PortletRequestListener information
svn changeset:10417/svn branch:6.2
---
diff --git a/WebContent/release-notes.html b/WebContent/release-notes.html
index 8fcf6343b1..b72d36f126 100644
--- a/WebContent/release-notes.html
+++ b/WebContent/release-notes.html
@@ -126,8 +126,14 @@ public class ColorPicker extends AbstractField {
- vaadin-maven-plugin can automatically update Vaadin 6.2 widgetsets based on Maven dependencies using the goal update-widgetset
- HttpServletRequestListener [TODO]
- PortletRequestListener [TODO]
+ HttpServletRequestListener
+
+ - Similar to TransactionListener but only related to a single Application. Called before and after every servlet request and provides access to HttpServletRequest and HttpServletResponse.
+
+ PortletRequestListener
+
+ - Similar to HttpServletRequestListener but for portlets. Called before and after every portlet request and provides access to PortletRequest and PortletResponse.
+
Sampler has been updated with many new samples.
Enhancements to various components:
@@ -138,7 +144,10 @@ public class ColorPicker extends AbstractField {
- MenuBar: Many enhancements: Individual items can be styled, support for separators, disabling of items, visibility of items.
- DateField: Support for lenient/non-lenient mode. A DateField is now by default in non-lenient mode (only accepts valid dates).
- Automatic integration tests for the supported servers
+ Automatic integration tests
+
+ - All Vaadin builds are now automatically tested on all supported servers.
+
Dozens of other small enhancements and bug fixes
@@ -150,46 +159,34 @@ widget sets and refresh your project in Eclipse. If you are upgrading from earli
6.2.0, notice that Vaadin 6.2 uses GWT 1.7.0 (included in the installation package). See
General Upgrade Notes for more details on upgrading.
-
-
-If you are using custom components (components from other than the
-DefaultWidgetSet) from an earlier version of Vaadin 6, you will need to upgrade the
-widget set definitions.
-
-[TODO]
+
+
+The widgetsets have been renewed and simplified in Vaadin 6.2 as described above. Existing projects
+where custom widgets (a custom widgetset) are used must be migrated when upgrading to Vaadin 6.2.
+Projects where the default widgetset is used do not need migration. For most
+projects this should be a quite painless upgrade.
+
+
+For applications where custom widgets are used (also applicable to widget projects):
- - If using a widget set from another project (most likely from a separate JAR file):
-
- - Get a widget set JAR compatible with Vaadin 6.2. If the new JAR does not contain a
- precompiled widget set (as it normally does not), you need to create a custom widget
- set for your project. The experimental eclipse plugin will create it for you
- automatically.
-
- - If the project has its own widget set:
-
- - Remove WidgetSet.java file, this is no more needed
- - If project has client-side components in its own source directory:
-
- - Remove getTag() method implementations from server-side components; tag
- names are no longer used. We have intentionally made the getTag() method
- final to make it easier to find them (they wont compile)
-
- - Annotate server-side components having client side counterpart with
- @ClientWidget(VClientSideCounterPart.class) annotation. Basically these are the
- same components that had the getTag() method previously.
-
- - If (combined) widget set uses widgets from other widget sets (most likely from a separate JAR file)
-
- - Update referenced widget sets to support 6.2
- - Add/keep necessary inherits tags in your combined widgetset (.gwt.xml file). Eclipse plugin will again try to automatically add these to your widgetset.
-
- - If you package a widget set as a JAR for usage in other projects:
-
- - Add an entry like Vaadin-Widgetsets: com.vaadin.incubator.fastlayouts.ws.FastLayoutsWidgetSet to JAR files MANIFEST.MF file. This helps tools to detect package as vaadin component package.
-
-
+ - Remove the getTag() method from all components and replace it with a @ClientWidget(VClientSideWidget.class) annotation. Tag names are no longer used to map the server-side and client-side part of the component. This is done automatically using the @ClientWidget annotation.
+- Remove the WidgetSet.java file. This file is no longer needed as the mapping between server and client side is done automatically using @ClientWidget.
+
+
+
+If you are using widgets from another project (typically in a separate JAR file):
+
+- Acquire a new JAR which is compatible with Vaadin 6.2 and add it to WEB-INF/lib. The widgetset compiler will automatically include the jar in your widgetset.gwt.xml during compilation if using Eclipse. For Ant/Maven you need to specify the location of the widgetset jars that you want to include in the application widgetset.
+
+
+
+If you package a widget set as a JAR for use in other projects:
+
+ - Replace getTag() with @ClientWidget and remove the WidgetSet.java as described above.
+ - Add a "Vaadin-Widgetsets: <fully qualified name of widgetset>" row to META-INF/MANIFEST.MF in the jar file. This enables the widgetset compiler to automatically detect and include the widgetset in other projects.
+