2 years back We have developed an application using GWT 1.4.6 and GWT-Ext 2.0.3 frameworks.
Now our management is thinking of upgrading these two frameworks.
But the Gwt-Ext website states that the development of Gwt-Ext has been superseded by smart GWT.
I just want to ask that if we update/upgrade from GWT 1.4.6 to GWT 2.2, whether Gwt-Ext 2.0.3 will work or not ?
if anyone have any experience in this please give me some inputs to move forward.
We had the same situation, we wanted to upgrade GWT 1.4 to 2.1.0 and we had GWT-Ext 2.0.3 which was the end of that project but there was 2.0.5 available though with minor changes.
The transition was not smooth but it was not also worst. We tried to attach new plug-in to our source in Eclipse and it complained about:
Removal of some unnecessary inherts in x.gwt.xml (main entry file)
The public folder was replaced with the new Ext 2.0.5 files
We were using ftr-gwt libarary where there were some mismatch with the method signatures and return types. But were simple.
And I don't remember running into any serious problems.
I believe it was in GWT 2.1 that Google updated their built in interface widgets dramatically. Because of this, my experience has been that the various widget libraries (GXT, SmartGWT) have had to update their libraries to support gwt 2.2. So my guess for your question is that GWT-EXT 2.0.3 probably will not work with GWT 2.2 or the newer 2.3.
Related
I have a customer requirement of GWT 2.4.0 due to a Java 5 limitation. Up until this latest Google Web Toolkit Plugin update I have been able to successfully use the plugin with GWT 2.4.0. I am seeing an error regarding a missing gwt-codeserver.jar and the GWT plugin says that GWT is not installed. Is there anything I can do as a workaround for using GWT 2.4.0 and the latest Eclipse/GWT plugin?
I had the same issue. I have downloaded the newest version of GWT just to copy the gwt-codeserver.jar in my SDK folder. So I didn't have the error anymore.
Also, in my debug/run configuration, I have removed the argument "-nosuperDevMode".
I was experiencing the same problem and like Gildas, I copied the gwt-codeserver.jar from GWT 2.6.0 into the 2.4.0 folder.
The next thing I had to do to get it to work was, when adding the 2.4 SDK, I had to point to the gwt2.4.0 folder as opposed to the parent "com.google.gwt.eclipse.sdkbundle_2.4.0.v201208080121-rel-r42" folder. Clean and build, good to go...with this problem, at least.
I have the task to do some work on our GWT 2.2 code base with
the GWT Config, etc, used, is long gone. And I must use Eclipse Kepler.
Does current GWT provide backward compatability that far?
Any thoughts?
The version of the Eclipse plugin is independent of the version of the SDK you use in your project. You can use the newest plugin with GWT projects that needs older versions of the SDK.
You have to set this up in the project properties.
Our project uses gwt 1.7 and jdk 1.5.0_13.
We need to add support for IE9 and above.
For that, we need to upgrade gwt to latest version (2.5) and, therefore, upgrade jdk as well.
While doing so, we are getting errors related to missing source codes in gwt jars (e.g. TimeOutException source code not found).
We have simply replaced the gwt 1.7 jars with latest ones. What else do we need to change?
Is there any guide explaining the migration procedure for gwt?
AFAIK there isn't any detailed guide explaining the migration. In the documentation project you have only a brief list of features and breaking changes for each version, it is very useful though.
You have many posts with the experience of users migrating from 1.7 to 2.0, but almost very old since 2.0 was released some years ago. There is very little info for migrations from 1.7 to the the last 2.5.
Said that, the main problem you will deal with is the change in the tools for dev and debug, so I recommend first to get used with these tools. Then you have to fix each single 'red' mark in your IDE project. Then you should look for 'yellow' marks in order to avoid using deprecated classes/methods. Finally you could consider replacing some code of your project with new features in 2.x like cell-widgets, layout-panels, etc, see the showcase.
The process will be tedious, but it is worth to have your project using last releases if you plan to maintain the application in the future.
BTW, there are plans to remove support for IE6, IE8 and even IE9 in future versions of GWT, in order to improve and modernize gwt and to support new html5 features. It will be gradual though: Solutions for people needing IE7/IE8 support in future GWT releases
I updated from 2.2 -2.5 yesterday and had 2 errors I had to overcome.
Jar file was for 2.2- I deleted it, switched to non GWT toolkit, and switched back. This updated(created) to correct jar.
source code problem- for some reason the run config was not transferred correctly. Since i had used a new workspace when updating i copied over the old path to the new workspace. (this was located under: Debug config--> Arguments--> Program arguments
Hope this helps :)
I am trying to upgrade GWT 1.7.0 to 2.0.0 but I get the following error.
Errors in 'jar:file:/C:/src/lib/gxt.jar!/com/extjs/gxt/ui/client/widget/Component.java'
As per the below link I did everything as shown.
How to upgrade GWT from 1.7 to 2.0
I am guessing there is no need to upgrade GXT. The GXT version I'm using is 1.2.5
Any ideas would be highly appreciated.
Definitely a compatibility problem with GXT and GWT. According to the GXT website you need to upgrade your gxt version to at least version 2.0.2. Try downloading GXT 2.2.5 (non-commercial version) and try it out with GWT 2.0 or even 2.4.
Reference to this is here
I decided to install GWT 1.5 in addition to installed GWT SDK 2.3; I've never had two GWT SDK on one IDE before... The question is...
Won't the two SDKs conflict if I have them both?
No you can easily have multiple SDKs installed. You can select the one you want to use for your project in the project properties (In Eclipse: Google->Web Toolkit->Use specific SDK)
You can have as many. You can set the default GWT SDK in Preferences->Google->Web Toolkit or you can override this per project (Project->Properties-Libraries)