mirror of
https://github.com/vaadin/framework.git
synced 2024-08-29 17:57:24 +02:00
325 lines
15 KiB
HTML
325 lines
15 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title>Vaadin 6</title>
|
|
<link rel="stylesheet" type="text/css" href="demo/css/styles.css" />
|
|
<!--[if IE]>
|
|
<link rel="stylesheet" type="text/css" href="demo/css/ie.css" />
|
|
<![endif]-->
|
|
</head>
|
|
<body>
|
|
|
|
<div id="header">
|
|
<h1>Vaadin – thinking of U and I</h1>
|
|
<div id="version">
|
|
<a href="javascript:history.go(-1);" title="Back to index page">Back</a>
|
|
</div>
|
|
</div> <!-- /header -->
|
|
|
|
<div id="content">
|
|
|
|
<p>Version @version@ built on @builddate@.</p>
|
|
|
|
<h2><a name="overview">Release Notes for Vaadin @version@</a></h2>
|
|
|
|
<ul>
|
|
<li><a href="#overview">Overview</a></li>
|
|
<li><a href="#changelog">Change Log</a></li>
|
|
<li><a href="#upgrading">General Upgrade Notes</a></li>
|
|
<li><a href="#upgrading-tk5">Instructions for Upgrading from IT Mill Toolkit 5</a></li>
|
|
<li><a href="#oophm">Package for the experimental GWT Out-of-Process Hosted Mode</a></li>
|
|
<li><a href="#known-problems">Important known problems in Vaadin @version@</a></li>
|
|
<li><a href="#requirements">Requirements</a></li>
|
|
</ul>
|
|
|
|
<p>Vaadin @version@ is a bugfix release for Vaadin 6. See the <a href="#changelog">Change
|
|
Log</a> below for a detailed list of issues fixed in this release.</p>
|
|
|
|
<p>For a list of new features and enhancements in the previous minor update release 6.1.0,
|
|
see the <a href="http://vaadin.com/download/release/6.1/6.1.0/release-notes.html">Release
|
|
Notes for Vaadin 6.1.0</a>.</p>
|
|
|
|
<p>Problem fixes and enhancements planned for upcoming releases can be found from the <a
|
|
href="http://dev.vaadin.com/roadmap">Vaadin Roadmap</a> in Vaadin Trac.</p>
|
|
|
|
<p>As always, when upgrading from an earlier version, you should recompile any custom
|
|
widget sets and refresh your project in Eclipse. If you are upgrading from earlier than
|
|
6.1.0, notice that Vaadin 6.1 uses GWT 1.7.0 (included in the installation package). See
|
|
<a href="#upgrading">General Upgrade Notes</a> for more details on upgrading.</p>
|
|
|
|
<h2><a name="changelog">Change Log</a></h2>
|
|
|
|
<p>The following issues have been fixed in this release:</p>
|
|
|
|
<ul>
|
|
<li><a href="http://dev.itmill.com/ticket/3095">#3095</a>: Sorting of a HierarchicalContainer does not work</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3141">#3141</a>: Multiple problems with tab scrolling</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3268">#3268</a>: ComboBox erroneus input is not always cleared</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3305">#3305</a>: Security key is blocked by certain firewalls</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3306">#3306</a>: Sample NotificationCustom does not seem to support serialization</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3320">#3320</a>: Create a session cleaner for GAE</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3343">#3343</a>: IE6 doesn't display cursor when tabbing into a TextField with an input prompt</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3345">#3345</a>: Combobox should show tooltip for dropdown button</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3349">#3349</a>: NPE when mainwindow is not set</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3351">#3351</a>: Sampler uses the same theme for all users</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3352">#3352</a>: Make a custom theme for Sampler theme select dropdown</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3363">#3363</a>: Subwindows are not added in order</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3365">#3365</a>: Form not resizing properly (not getting narrower)</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3383">#3383</a>: ComboBox input prompt style is removed when input prompt is active</li>
|
|
<li><a href="http://dev.itmill.com/ticket/3388">#3388</a>: Deploying portlets from two separate wars on the same page in Liferay does not work</li>
|
|
</ul>
|
|
|
|
<h2><a name="upgrading">General Upgrade Notes</a></h2>
|
|
|
|
<p>When upgrading from an earlier version of the Vaadin library, you should always do the following:</p>
|
|
|
|
<ol>
|
|
<li>Install the new Vaadin JAR to your project</li>
|
|
<ul>
|
|
<li>If using the Vaadin Plugin in Eclipse, download and select the new version in project preferences.</li>
|
|
</ul>
|
|
<li>Install new GWT JARs if the GWT version has changed</li>
|
|
<ul>
|
|
<li>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 (<a href="http://dev.vaadin.com/ticket/3286">#3286</a>).
|
|
</ul>
|
|
<li>If you have custom widget sets, recompile them with the new Vaadin library using the included GWT compiler</li>
|
|
<li>If using the Eclipse IDE:
|
|
<ol type="a">
|
|
<li>Refresh the Eclipse project by selecting the project folder and pressing <strong>F5</strong></li>
|
|
<li>Restart the application server</li>
|
|
</ol>
|
|
</ol>
|
|
|
|
<p>Using the Vaadin project facet in the Eclipse IDE does the steps 1 and 2 automatically.</p>
|
|
|
|
<h2><a name="upgrading-tk5">Instructions for Upgrading from IT Mill Toolkit 5</a></h2>
|
|
|
|
<p>While the Vaadin 6 API is otherwise mostly backward-compatible with IT Mill Toolkit 5.4, the
|
|
change of the product name has made it necessary to reflect it in the Java package names,
|
|
some name prefixes, and some other details.</p>
|
|
|
|
<h3>Server-side Upgrade Instructions</h3>
|
|
|
|
<ul>
|
|
<li>Java Package names have changed:</li>
|
|
<ul>
|
|
<li>In all Java files using IT Mill Toolkit, rename package prefix <tt>com.itmill.toolkit</tt> → <tt>com.vaadin</tt></li>
|
|
<li>You also need to update the <tt>web.xml</tt> deployment descriptor:</li>
|
|
<ul>
|
|
<li>The servlet class is now <strong>com.vaadin.terminal.gwt.server.ApplicationServlet</strong>.</li>
|
|
</ul>
|
|
</ul>
|
|
|
|
<li>Changes in themes:
|
|
<ul>
|
|
<li>Rename <tt>WebContent/ITMILL</tt> → <tt>WebContent/VAADIN</tt></li>
|
|
<ul>
|
|
<li>If you have extracted the built-in themes and widgetsets in IT Mill Toolkit JAR to the folder to have them served statically by the server, remove the old content and re-extract from Vaadin JAR.</li>
|
|
<li>This may require changes to build scripts for custom widgetsets, as well as to any code that relies on the old naming (it is discouraged but possible).</li>
|
|
</ul>
|
|
<li>The new "<tt>reindeer</tt>" theme is the default theme in Vaadin; the old
|
|
"<tt>default</tt>" theme in IT Mill Toolkit 5 has been renamed as "<tt>runo</tt>"</li>
|
|
<ul>
|
|
<li>There is no longer a theme with name "<tt>default</tt>"</li>
|
|
<li>In your custom theme, replace:
|
|
<table><tr><td></td><td><tt>@import "../default/styles.css";</tt></td></tr>
|
|
<tr><td align="right">→</td><td><tt>@import "../reindeer/styles.css";</tt></td><td>if you wish to use the new default theme,</td></tr>
|
|
<tr><td align="right">or →</td><td><tt>@import "../runo/styles.css";</tt></td><td>if you wish to use the old default theme.</td></tr></table></li>
|
|
<li>Use the new default theme with <tt>setTheme("reindeer")</tt> and the old one with <tt>setTheme("runo")</tt>.</li>
|
|
</ul>
|
|
<li>CSS class names now start with "<tt>v-</tt>" prefix instead of "<tt>i-</tt>"</li>
|
|
<ul>
|
|
<li>Search and replace "<tt>.i-</tt>" → "<tt>.v-</tt>" in custom themes </li>
|
|
</ul>
|
|
</ul>
|
|
|
|
<li>Embedding Vaadin applications in web pages:</li>
|
|
<ul>
|
|
<li>The name of the JavaScript variable used for launching applications has changed from "<tt>itmill.toolkitConfigurations</tt>" → "<tt>vaadin.vaadinConfigurations</tt>"</li>
|
|
</ul>
|
|
|
|
<li>Other changes in naming:</li>
|
|
<ul>
|
|
<li>Rename references to <tt>translateToolkitUri()</tt> → <tt>translateVaadinUri()</tt> method in <strong>ApplicationConnection</strong> class.
|
|
</ul>
|
|
|
|
</ul>
|
|
|
|
<h3>Client-side Upgrade Instructions</h3>
|
|
|
|
<p>The following changes are relevant only if you have developed or integrated custom
|
|
client-side widgets with Google Web Toolkit (GWT).</p>
|
|
|
|
<ul>
|
|
<li>GWT 1.7 is required for compiling custom widgets (optional)</li>
|
|
<ul>
|
|
<li>You need to upgrade GWT</li>
|
|
<li>The GWT Compiler class name has changed:</li>
|
|
<ul>
|
|
<li>Replace <tt>com.google.gwt.dev.GWTCompiler</tt> → <tt>com.google.gwt.dev.Compiler</tt> in your widget set build script (Ant) or launch configuration (Eclipse).</li>
|
|
<li>Replace the output directory argument for the compiler with the new WAR output argument: <tt>-out</tt> → <tt>-war</tt>. The directory parameter for the argument remains unchanged.</li>
|
|
</ul>
|
|
</ul>
|
|
|
|
<li>The "<strong>I</strong>" (IT Mill) prefix in client-side widget classes has been changed to "<strong>V</strong>" (Vaadin), for example: <strong>IButton</strong> → <strong>VButton</strong>.</li>
|
|
<li>Rename <strong>IToolkitOverlay</strong> → <strong>VOverlay</strong>
|
|
</ul>
|
|
|
|
<h2><a name="gae">Notes and Limitations for Google App Engine</a></h2>
|
|
|
|
<p>The following instructions and limitations apply when you run a Vaadin application
|
|
under the Google App Engine.</p>
|
|
|
|
<ul>
|
|
<li><p>Applications must use <b>GAEApplicationServlet</b> instead of
|
|
<b>ApplicationServlet</b> in <tt>web.xml</tt>.</p></li>
|
|
|
|
<li><p>Session support must be enabled in <tt>appengine-web.xml</tt>:</p>
|
|
|
|
<pre> <sessions-enabled>true</sessions-enabled></pre>
|
|
</li>
|
|
|
|
<li><p>Avoid using the session for storage, usual App Engine limitations apply (no
|
|
synchronization, i.e, unreliable).</p></li>
|
|
|
|
<li><p>Vaadin uses memcache for mutex, the key is of the form
|
|
<tt>_vmutex<sessionid></tt>.</p></li>
|
|
|
|
<li><p>The Vaadin <b>WebApplicationContext</b> class is serialized separately into memcache
|
|
and datastore; the memcache key is <tt>_vac<sessionid></tt> and the datastore
|
|
entity kind is <tt>_vac</tt> with identifiers of the type <tt>_vac<sessionid></tt>.</p></li>
|
|
|
|
<li><p>DO NOT update application state when serving an <b>ApplicationResource</b> (e.g <b>ClassResource</b>.<i>getStream()</i>).</p></li>
|
|
|
|
<li><p>AVOID (or be very careful when) updating application state in a
|
|
<b>TransactionListener</b> - it is called even when the application is not locked and
|
|
won't be serialized (e.g <b>ApplicationResource</b>), 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)</p></li>
|
|
|
|
<li><p>The application remains locked during uploads - a progress bar is not possible</p></li>
|
|
</ul>
|
|
|
|
<h2><a name="oophm">Package for the experimental GWT Out-of-Process Hosted Mode</a></h2>
|
|
|
|
<p>We provide a separate (platform independent) installation package
|
|
(<tt>vaadin-oophm-@version@.tar.gz</tt>) for the
|
|
experimental Out of Process Hosted Mode (OOPHM) of GWT, which allows
|
|
debugging client-side code in GWT Hosted Mode with a regular web
|
|
browser. Using the OOPHM requires installing a browser plugin (available
|
|
for Mozilla Firefox, IE, and WebKit). See the manual section on OOPHM
|
|
for more details.</p>
|
|
|
|
<p>The Linux version of GWT Hosted Mode Browser is no longer compatible with Vaadin (<a
|
|
href="http://dev.vaadin.com/ticket/2299">#2299</a>), so the OOPHM is the only option for
|
|
debugging in hosted mode in Linux.</p>
|
|
|
|
<p>The GWT 1.7.0 version included in the OOPHM package is a custom
|
|
build from GWT trunk and is not 100% compatible with the official GWT
|
|
1.7.0 release (<a href="http://dev.vaadin.com/ticket/3270">#3270</a>).</p>
|
|
|
|
<p>As the OOPHM package is experimental and because there are
|
|
differences between the version packaged with Vaadin and the official
|
|
version of GWT, you should use it only for debugging purposes during
|
|
development. For production use, and generally when you absolutely do
|
|
not need to debug using OOPHM, you should compile your custom widget
|
|
sets with the regular Vaadin package for your platform.</p>
|
|
|
|
<h2><a name="known-problems">Important known problems in Vaadin @version@</a></h2>
|
|
|
|
<ul>
|
|
<li><p><a href="http://dev.vaadin.com/ticket/1155">#1155</a>:
|
|
Uncompressing the installation package fails in Windows if using the
|
|
default Zip uncompression. Uncompression gives (in Windows Vista) an
|
|
error message about too long filenames, and a more obscure message in
|
|
other versions of Windows. Workaround: use <a
|
|
href="http://www.7-zip.org/">7-Zip</a> or some other good unzip
|
|
program for Windows.</p></li>
|
|
|
|
<li><p><a href="http://dev.vaadin.com/ticket/2299">#2299</a>: The
|
|
Hosted Mode Browser does not work in Linux for debugging client-side
|
|
GWT code. You need to install the experimental OOPHM package instead
|
|
(see above) for development. For production, you should use the regular
|
|
package for Linux.</p></li>
|
|
</ul>
|
|
|
|
<p>For other known problems, see open tickets at developer site <a
|
|
href="http://dev.vaadin.com/">dev.vaadin.com</a>.</p>
|
|
|
|
<h2><a name="requirements">Requirements</a></h2>
|
|
|
|
<p>Vaadin is available for the following operating systems:</p>
|
|
|
|
<ul>
|
|
<li>Windows (see the Zip installation notice above)</li>
|
|
|
|
<li>Linux</li>
|
|
|
|
<li>Mac OS X Tiger (mac) or Leopard (leopard)</li>
|
|
|
|
<li>Other UNIX operating systems, such as Sun Solaris, using the installation package
|
|
for Linux.</li>
|
|
</ul>
|
|
|
|
<p>Vaadin supports Java Servlet API 2.3 and later versions and should work with
|
|
any Java application server that conforms to the standard. It supports the following
|
|
application servers:</p>
|
|
|
|
<ul>
|
|
<li>Apache Tomcat, version 4.1 or later</li>
|
|
<li>BEA WebLogic® Server, version 9.2 or later</li>
|
|
<li>IBM WebSphere® Application Server, version 6.1 or later</li>
|
|
<li>JBoss Application Server, version 3.2.8 or later</li>
|
|
<li>Jetty, version 5 or later</li>
|
|
<li>Glassfish, version 2 or later</li>
|
|
</ul>
|
|
|
|
<p>Vaadin supports the following browsers for using the applications made with
|
|
it:</p>
|
|
|
|
<ul>
|
|
<li>Mozilla Firefox 3</li>
|
|
<li>Internet Explorer releases 6, 7, and 8</li>
|
|
<li>Safari 3 and 4</li>
|
|
<li>Opera 9.6 and 10</li>
|
|
</ul>
|
|
|
|
<p>The support for browsers follows the support by GWT. The browsers are supported on both
|
|
Windows and Mac, if available. Firefox is supported also on Linux (Opera 10a1 works also
|
|
on Linux though also suffers from <a
|
|
href="http://dev.vaadin.com/ticket/2652">#2652</a>). There may be differences between the
|
|
exact versions of the supported browsers that may cause incompatibility with applications
|
|
made with Vaadin.</p>
|
|
|
|
<p>The following browsers are not supported but have been found to
|
|
work to a large degree:</p>
|
|
|
|
<ul>
|
|
<li>Safari 2, and 4 beta</li>
|
|
<li>Firefox 2</li>
|
|
<li>Google Chrome 1.0.x (available only for Windows)</li>
|
|
<li>iPhone (firmware 2.2)</li>
|
|
<li>Midori (0.1.2)</li>
|
|
<li>Epiphany (2.22.3), Galeon, and other Gecko-based browsers. Also WebKit-based Epiphany (2.22.3) works.</li>
|
|
<li>Konqueror 4.2 (3.5.x does not work)</li>
|
|
<li>Nokia Internet Tablet N800 and N810 (ITOS 2008, Opera-based browser).</li>
|
|
</ul>
|
|
|
|
<p>The reported versions are those that have been tested, though other versions may work
|
|
as well.</p>
|
|
|
|
<p>Nokia E-series phones, such as E90, have been known to work with older versions, but
|
|
not with Vaadin 6. Links, Lynx, and other text-based browsers do not
|
|
work.</p>
|
|
|
|
</div> <!-- /content-->
|
|
|
|
|
|
<div id="footer">
|
|
<span class="slogan">Vaadin – thinking of U and I<span>
|
|
</div> <!-- /footer -->
|
|
|
|
</body>
|
|
</html>
|