Gwt what is new

How are others experiences on this, has anyone moved from GWT to Angular with a small team and how are the experiences from a resource point of view to that? But I've seen Vaadin vaadin. Can't deny the value GWT brings in through type-safety. If there is a way to overcome the slow compilation on GWT, it's still a great idea and a product, and will be for a long time.

So worth finding an answer to the question I believe.. At this point of time, GWT is not a prudent decision for any new project. There are 2 primary reasons.

Google tries to distant itself from Java as far as it can. Google prefers Kotlin over Java in Android. Angular is far superior in every way. It provides type safety. Any JavaScript code is a really typescript code. So the libraries that were created for JavaScript over the decade works seamlessly with Angular.

For GXT currently at version 4. Unfortunately there's no public roadmap from Sencha to support GWT 2. We have a medium size project based on GWT in our company; It's a mature software, with more than , users and has performed well so far. However, GWT technology seems to become obsolete and I personally see no bright future for it, in competition with brand-new client-side rivals such as Angular.

GWT had another minor release 2. I have had a relatively good experience using GWT so far and our clients get used to it as well, but the problem is that you might wake up someday and find out that a new version of Chrome or Firefox is released that no longer supports GWT mutations. Knowing that we gradually started migrating our client code to Angular which is of course very similar to GWT in the soul Both are complete UI Frameworks; GWT transforms java to JS, while Angular does the same with TypeScript; both projects are supported by Google, and there are lots of widgets for both available out there.

I suggest that, despite all its costs, moving from GWT to another more up-to-date technology is inevitable and crucial IF the remaining of your software's lifetime is more than one or two years. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 2 years, 11 months ago. Active 10 months ago. Viewed 10k times. We have multiple product developed primarily using GWT and currently used by our end customers. Improve this question. J2CL get public today: groups. Several modules and frameworks have already prepared to work with J2CL. For the StockWatcher project, you will run webAppCreator with the following parameters.

Parameter Definition Example -out The directory to place the generated files. StockWatcher -junit The fully-qualified path name to junit. You can download JUnit at their sourceforge project page, or you can use the version that ships with Eclipse. StockWatcher Create the StockWatcher application. At the command line, run webAppCreator. Enter the command below on a single line.

The example is shown on multiple lines only to improve readability. Replace the junit. StockWatcher Note: The -junit argument is optional. GWT webAppCreator generates the project subdirectories and files you need to get started.

Files Created StockWatcher. Eclipse Files Created. Testing the default project components To check that all the project components were created, run the starter application in development mode. In the toolbar, click the Run button Run as Web Application. When the development mode tab opens, right-click on the URL to copy it. Paste the URL into your browser of choice. Running the development mode code server not from Eclipse webAppCreator creates an ant build file with a target for running the application in development mode.

Connecting to the development mode code server with and without Eclipse Once you have started the development mode from Eclipse or using the build. Starter Application When you create a new web application with GWT, by default it creates a simple, starter application as shown below. The host page references the application style sheet, StockWatcher. For example, imports work. This makes Java method names available in browser debuggers at the expense of code size.

Also available in Super Dev Mode. They should be unboxed before being passed to Java. GWT apps that inherit the com. Logging module have different default behavior for messages logged using the java. PopupLogHandler and SystemHandler are no longer enabled by default. If the CssResource. The rpc. XserializeFinalFields configuration property turns on experimental support for serializing final fields. However, most current browsers no longer support Dev Mode plugins. Compiling is much faster after the first compile.

Compiling is skipped altogether if no files have changed. When enabled, Super Dev Mode writes stub. This feature is automatically enabled when launched via DevMode. Messages logged using java. Removed flags: -standardsMode , -nostandardsMode , -quirksMode. A complete list of changes can be found here. This release includes minor updates to silence unnecessary debugging warnings. See the release notes for 2.

This release enabled the Super Dev Mode hook by default, updated the sample Maven POMs, included a Firefox memory leak fix for Dev Mode, and a few other minor regressions noted during release candidate testing. This release fixed an incompatibility with the Google Plugin for Eclipse, improved uncaught exception handling, and reverted some backwards-incompatible changes made since GWT 2.

Flags have been cleaned up for consistency, but the old flags are still supported for backward compatibility. The ie6 permutation which also handles IE 7 is now disabled by default. Added the ie10 permutation. However, note that workarounds needed for previous versions of IE may no longer be necessary. Element methods that return sizes in pixels automatically convert subpixel values to int for backward compatibility. Element which has long been deprecated now take a com.

Element instead. Security: with 2. For even more detail, see Changelists up to 2. This release includes some minor bug fixes found in the release candidate. The GWT team recently learned that the Security vulnerability discovered in the 2. A more complete fix was added to the 2. This is release candidate 2 of GWT 2.

This is release candidate 1 of GWT 2. In addition to the items mentioned above, see for a list of bug fixes and enhancements for 2. See the release notes below for the full list of features and bug fixes included in this release. The 2. See the complete list of bug fixes and enhancements for 2. See the complete list of breaking changes in the GWT issue tracker. Recently, the GWT team discovered a cross-site scripting vulnerability in the 2.

This vulnerability was partially fixed in the 2. See the GWT issue tracker for the complete list of bug fixes and enhancements in this release. This is a preview release of 2. Use the following steps:. This release contains big changes to improve developer productivity, make cross-browser development easier, and produce faster web applications.

This release adds support for Mac OS X version This release adds explicit support for Internet Explorer 8, Firefox 3. In all other respects, it is very similar to GWT 1. Note, however, that this release is version 1. GWT 1. For example, you cannot set the height and width of a widget relative to its parent if its parent is a table cell, and StackPanel takes up much more vertical space than it should in Internet Explorer. All of our samples have been reverted back to quirks mode, and the applicationCreator defaults to quirks mode when creating a new GWT app.

You can still use standards mode for your GWT app, but please be aware that you may notice some layout issues. If you are switching an app from quirks mode to standards mode, your CSS styles might be applied differently, which could also affect your application.

We will continue to address standards mode support in future GWT releases. This release candidate is, in a word, huge. This release includes numerous bugfixes and a few important changes. If you are upgrading from GWT 1. See the GWT issue tracker for the complete list of bug fixes in this release. There are some important behavioral and potentially breaking API changes; if you read nothing else, please read these following sections!

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. Beginning with version 1. While this new behavior may seem annoying at first, rest assured that fixing your code to avoid RPC warnings will result in a smaller, faster, and more reliable app. Previously, if you declared one particular component type via gwt.

For example, placing a Date in an ArrayList of String might work. This type of code is less likely to work now and will likely become more strict in the future. Make sure collections only contain the declared item type or subtypes thereof. Serializable equivalent to IsSerializable. This should improve server-side interoperability and remove much of the need for DTOs. RPC has never actually serialized final instance fields, but now it explicitly warns about the existence of such fields unless they are also transient.

Thus, the warning can be addressed by making final instance fields transient as well, or it can be suppressed via a module property. Attempting to serialize classes that contain native methods will cause UnsatisfiedLinkErrors if such methods are called in server-side code. This release also includes API changes that may require minor tweaks to existing code. Any such changes that affect you should only take a few minutes to rectify.

See the GWT issue tracker for the complete list of enhancements in this release. This version has no new functionality, but we did make a lot of changes to get the source code and build scripts into presentable shape to prepare for ongoing open source development.

This is the official GWT 1. It includes all of the enhancements and bug fixes from GWT 1. There are no breaking changes to pre The method addHeader was renamed to setHeader to more clearly reflect its intent. You will only be affected by this change if you are using the new HTTP functionality available as of build 1. Between this build and the subsequent GWT 1.

See the GWT issue tracker for the complete list of enhancements and bug fixes in this release. Fixed Issues Issue - Servlet container problems due to gwt-user. See the appendix of fixed issues for the nitty-gritty list of things that we have fixed in this release, including smaller issues.

The list of issues below is a short synopsis of all of the major and minor issues fixed in this release. See the online GWT issues database for the important common issues.

Added support for Java language levels 9, 10, and Deprecations Elemental has been officially deprecated - it is still included in this release, but may not appear in future releases. Removed NoSuchMethodException emulation.

Bug fixes Fixes Arrays. Updates globals for Firefox version Native JsMethods allowed to coexist with implementations with the same name. Make sure lambdas box, unbox and insert erasure casts when necessary. Arrays now implement Cloneable Link backing errors together with a cause attribute, start tracking suppressed errors in addition to the cause in underlying error object.

Flow Emulate javax. Add when-linker-added element definition Add Reader and StringReader emulation. Remove GWT version check. Update unmodifiableList to throw on Java8 methods.

Disable DataflowOptimizer by default and emit a warning when used For more detail, see the commit log. Release Notes for 2. Apply HtmlUnit workaround ensuring that window. Externalizable Added emulation for java.

Array JSO. Bug fixes Fix loading bug in waitForBodyLoaded. Fix bad rewriting of default methods. Make native NativeRegExp refer to the iframe instance. Fix incorrect comparison of object arrays in Arrays. Fixed NullPointerException in handling of Jetty arguments Fixes a bug where JsOptional on override may fail Clear persistent unit cache when relevant options change.

Rescue types represented as natives when supertypes cross JS boundaries. Prevent errorneous floating point expression optimization. Fix the implementation of Stream.

Do not ignore return values of streams. Fix ICE due to intersection types appearing as erasure casts. Fix bad varargs conversion in method reference. Fix: Add role attribute to last sortable column header Properly preserve names in overrides of native methods. Make Array. Improve primitive cast optimizations. Update global blacklist to chrome Allow native classes implement native interfaces with overlays.

Fix missing bridges for default methods and functionnal expressions. Fix incorrect property copying for native JsType subclasses. Fix toString dispatch for subtypes of native JsTypes. Miscellaneous Improve JsInterop error messages on native type fieds. Update globals for Chrome Deprecation Deprecate dangerous RootPanel clear boolean. Fix an issue around DevMode server jetty restart. Fix an issue in super dev mode with changing compiler options not triggering full recompiles.

Added missing command line parameters to DevMode entry point Fixed a performance regression in String. Fix memory leak with Java 8 compilation. Source level set to Java 8. This could break existing build if an interface is changed to turn a non-default method into a default method.

Deprecations Classic dev mode deprecated. You can switch back to dev mode for your test cases temporarily by passing gwt. Use patched JDT to circumvent memory leak when compiling for Java 8.

Disallow non-native JsProperty on static methods. Remove legacy JsInterop. Add JsOptional annotation disallowed on primitive typed parameters. Allow JsOverlay on effectively final methods. JDK emulation Emulate java. Emulate Objects. Fix Math. Emulate Character. Emulate CharSequence. Emulate java. Emulate Java 8 API of java. Arrays , java. ArrayDeque , java. BigInteger , java. BitSet , java. Comparator , java. Iterator , java.

Iterable , java. Map , java. Logger , java. PrimitiveIterator , java. Spliterator , java. Update apache commons-collections to 3. JsonValue is now serializable. JsInterop has graduated from experimental. See final JsInterop specification.