When was gwt released

The CssResource. The ui:data tag has new attributes: mimeType and doNotEmbed. LinkedHashSet may be serialized without a serialization policy. Support overridden methods and generics better. Upgraded to CLDR Updated support for typed arrays.

Added History. Fixed an issue with Window. The deprecated com. Various bugfixes and minor improvements. The first compile no longer happens at startup. Chrome reloads the page faster while debugging. Sourcemap file size is reduced. Fixed a startup failure caused by locked directories on Windows. Better error reporting for compile errors while running tests. This can be overridden using -sourceLevel 6 GWT Development Mode will no longer be available for Chrome sometime in , so we improved alternate ways of debugging.

There are improvements to Super Dev Mode, asserts, console logging, and error messages. IE10 is now a separate permutation. A GwtIncompatible annotation may be used to mark classes, methods, and fields that the GWT compiler should ignore.

Any annotation with this name can be used, regardless of package. Arguments may be specified multiple times on the command line and the last one wins. The deprecated -out flags were removed Added flags for turning specific optimizations on and off. Combined with the includeSourceMapUrl config property, it is possible to set up source-level debugging outside Super Dev Mode. Catching and rethrowing a JavaScript exception no longer wraps it in a Java exception so the console will print it correctly, etc.

Failed assertions stop in the browser's debugger if open Various code size improvements. Fragment merging is more reliable, works with soyc reports GWT.

This behavior can be reverted by inheriting SynchronousFragmentLoadCallback. Other fixes; see the issue tracker for more. Addition of a result caching API that generator writers can use r, r Drastic improvement in RPC performance in development mode by providing a development-mode-only implementation for RPC.

Addition of source map support. See this document for more details. Reduction of overhead of Java types in compiler output r Addition of pre-deserialization type checking to reduce the number of error messages that occur from attempts to invoke an RPC method with type mismatches r DateCell now accepts a TimeZone as a constructor arg.

Improvements in reporting of JavaScriptExceptions in development mode to include the method name and arguments. CssResource defs now support multiple values r CLDR data updated to v2. Added simple and global currency patterns r Various fixes to stabilize the compiler output on null no change recompiles. Added the -Dgwt. Added GWT emulation for Float.

Added support for typed arrays r Greatly reduce symbol map size by removing already-pruned symbols from the map. Deprecated methods AbsractCellTable. See r and r for details. See r Use Tree[Item]. GwtTransient will now work for any annotation that with that simple name for example, com. This prevents library writers from having their library depend on the GWT distribution.

This is useful for debugging and testing r The permutation mapping file is now generated as part of every compile. See r for more details. The following dependencies have been updated to the following versions: Eclipse JDT 3. The compiler metrics aspect of the Compile Report has been disabled by default. The compile report results in instability in the Compile Report.

To add compiler metrics to the compilation report, use the -XcompilerMetrics flag. The compiler. Known Issues Clicking in the navigation area but not on an actual item of the Showcase sample results in the navigation area going blank.

This results in faster startup time for iterative development. Scrolling DataGrid : The new DataGrid widget supports vertical scrolling with a fixed header above and footer below. Design Time Support : The Beans. Security vulnerability in GWT 2. It can be installed via the JBoss Update site. It is enabled by default for new Cloud-Connected Android Projects only.

General Enhancements Added IE9 support. See the IE9 - Tips and Tricks doc for more information. This warning occurs because although UiBinder HTML rendering has been updated to support SafeHtml , by default this is turned off set to false , due to some minor bugs. You can determine whether you are affected by the known bugs by checking the public bugs , , and More information on this feature can be found here. Version 2.

While Java 1. These errors can be ignored as they are related to classes that are most likely not used by your app, and will be omitted during compilation, or while running in dev mode.

Fixed Issues Image. List interface Safari 5 fails to execute non-integral right-shifts correctly Release Notes for 2. Noteworthy Fixed Issues Standard.

Potentially breaking changes and fixes Fixed a bug in how code generators collect method arguments from generated source, which impacted the Messages interfaces generated for UiBinder template files. In GWT 2. Most GWT applications will be unaffected, but external systems relying on these names will need to be updated. The development mode server will, by default, only bind to localhost which will break cross-machine debugging. You can get the old behavior by specifying -bindAddress 0.

Please see issue for more details. For webAppCreator-generated ant files, you can pass this with ant -Dgwt. The official doc is still in progress, but for an overview please see Layout Design on the wiki. UiBinder now directly supports LayoutPanel. The -web argument is now deprecated in favor of -prod , consistent with the terminology change from web mode to production mode.

The junitCreator command line utility has been removed. This could break native code that looks iterates through the properties of such an object. The generated reports are now written to the private extra directory. This eliminates an unlikely security risk of accidentally deploying compile reports to a publicly accessible location. Various Swing UI improvements. Things that are changing with GWT 2.

You download the same zip file for every development platform. This is made possible by the new plugin approach used to implement development mode see below. Development mode is supported through the use of a native-code plugin called the GWT Developer Plugin for many popular browsers. In other words, you can use development mode directly from Safari, Firefox, Internet Explorer, and Chrome.

Imagine having to download a whole movie before being able to watch it. With code splitting, you can arrange to load just the minimum script needed to get the application running and the user interacting, while the rest of the app is downloaded as needed. Previously, widgets had to be created and assembled programmatically, requiring lots of code. Now, you can use XML to declare your UI, making the code more readable, easier to maintain, and faster to develop. The Mail sample has been updated to show a practical example of using UiBinder.

Bundling of resources via ClientBundle. GWT introduced ImageBundle in 1. ClientBundle generalizes this technique, bringing the power of combining and optimizing resources into one download to things like text files, CSS, and XML. This means fewer network round trips, which in turn can decrease application latency — especially on mobile applications.

As a result, running unit tests required starting an actual browser. As of 2. Instead, it uses HtmlUnit as the built-in browser. Because HtmlUnit is written entirely in the Java language, there is no longer any native code involved in typical test-driven development. The development mode entry point has changed a few times since GWT 1. As of GWT 2. Sorry to keep changing that on ya, but the good news is that the prior entry point still works. But, to really stay current, we recommend you switch to the new DevMode entry point.

In other words, to start development mode from the command-line, type ant devmode. HtmlUnit does not attempt to emulate authentic browser layout. Consequently, tests that are sensitive to browser layout are very likely to fail. However, since GWTTestCase supports other methods of running tests, such as Selenium, that do support accurate layout testing, it can still make sense to keep layout-sensitive tests in the same test case as non-layout-sensitive tests.

Versions of Google Plugin for Eclipse prior to 1. You can fool it by sym linking or copying gwt-dev. The way arguments are passed to the GWT testing infrastructure has been revamped.

This change likely does not affect typical test invocation scripts, but if you do use -Dgwt. Release Notes for 1. Fixed Issues Allow hosted mode using a 1. Potentially breaking changes and fixes This release includes explicit support for IE8, which has some significant behavioral changes from prior versions of IE.

These changes are great enough that the new value ie8 has been added for the user. If you have deferred binding rules i. For more information, see the technical notes. JSP compilation should work out of the box in hosted mode. Application startup should be handled by calling the new History.

Fields marked final in serializable types will now generate a warning; the fact that they were not being serialized was a source of confusion. Mark such fields both final and transient to avoid the warning. Instance methods on overlay types cannot be accessed from JSNI. This used to work in hosted mode, but failed at runtime in web mode. The hosted mode server no longer serves hosted. This file is tightly coupled with the hosted mode implementation and was not meant to be user overridable.

General Enhancements Collections. Improved exception stack traces in hosted mode when JSNI stack frames are present. Fixed Issues Fixed the relationship between the coordinates returned by Element. Potentially breaking changes and fixes DOM. This means that attempting to retrieve an attribute for an event that does not support that attribute will now throw an assertion error instead of returning a coerced value.

Most notably, the click event throws an assertion error if you attempt to get the mouse button that was clicked. The return value of DOM. In hosted mode, an assertion error will be thrown if the attribute is not defined for the given event, as described in the previous bullet. Opera specific code has been upgraded to work with Opera 9. Specifically, some widgets may not be able to receive focus. Calls to History.

Fixed a bug in the benchmarking that prevented source code from showing up in reports. This message has now been removed because screen readers and some browsers would display this content to end users.

New Features DOM. Collection is now implemented. This allows your application to startup before certain resources such as images are fully loaded. Linux hosted mode should be less crashy. Warn if no concrete, serializable subclasses can be found for a given type declared in a RemoteService interface. RPC now generates a serialization policy file during compilation.

The serialization policy file contains a whitelist of allowed types which may be serialized. Its name is a strong hash name followed by. This file must be deployed to your web server as a public resource, accessible from a RemoteServiceServlet via ServletContext. If it is not deployed properly, RPC will run in 1. If you have subclassed Panel, please carefully review the new documentation for Panel. Retractions from 1. All changes relative to 1. One of these warnings would be issued when a class containing native methods was found to be serializable.

This warning now only applies to automatically serialized types; types with custom serializers will no longer trigger this warning.

This change caused code that worked in 1. In this release, the error has been downgraded to a warning. Critical Changes to RPC In previous versions, the RPC subsystem was too lenient and failed to warn at compile time about potential though unusual edge cases that could in theory cause problems at runtime.

Bad code that happened to work before might not now Previously, if you declared one particular component type via gwt. Warn about missing gwt. In the past, a missing gwt. Now that this bug has been fixed, you can achieve significant reduction in the size of your compiled output by fixing these warnings.

Warn about serializable subclasses that violate the serialization restrictions An RPC warning is emitted for classes that are assignable to IsSerializable or Serializable but that lack a default constructor or contain fields which cannot be serialized. It is important to resolve these warnings to avoid rare but confusing situations in which exceptions would be thrown at runtime.

Warn about non-transient, final instance fields RPC has never actually serialized final instance fields, but now it explicitly warns about the existence of such fields unless they are also transient. Warn about local and non-static nested types that implement IsSerializable or Serializable RPC has never serialized these kinds of classes and will now generate a warning.

Warn about native methods in serializable classes Attempting to serialize classes that contain native methods will cause UnsatisfiedLinkErrors if such methods are called in server-side code. Script load order is now handled automatically and these expressions are ignored. A warning will be issued in hosted mode. For reference, see here. Unfortunately, this would allow code to work in hosted mode that could fail in unexpected ways in web mode. Hosted mode will now throw a HostedModeException if you try to pass an incompatible type.

See here for more details. JavaScriptObject Although subclassing JavaScriptObject is not supported, some people do so anyway at their own risk : Please note that the existing int constructor has been removed in favor of a protected no-arg constructor. DeferredCommand The add method is deprecated in favor of addCommand in order to support the new IncrementalCommand interface. Had we simply added a new method overload, existing code that passed in a null literal would have failed to compile.

The new addPause method should be used instead of add null. One potentially breaking change, however, is that an exception is thrown if an attempt is made to remove the primary style name of a widget using removeStyleName. See the UIObject documentation for a full explanation. The above optimizations combined with ImageBundle , make it possible for GWT-based applications to load surprisingly quickly.

To see for yourself, check out startup time of the Mail sample. Cross-site script inclusion is now supported. Show original message. Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message. Since last months there is almost no progress on milestone for GWT 2. Frank Hossfeld. Atm the community is very active. Besides that, many new frameworks are evolving.

Jeff Zemsky. Frank - Thanks for the reply, but it would be good to understand the plans to complete the GWT 2. Any insight there? Luis Fernando Planella Gonzalez. It has always been said that GWT is active when similar questions are asked in the forum.