Re: (New to GWT) Need advise in migrating current app from GWT 1.7.0

Hello ssg,

Even Iam sailing in the same boat. I have to choose GWT 2.6 or 2.7 to migrate the old GWT 1.6.
Did you get any result whether gwt-ext version 2 will workout for GWT 2.7? If we try to replace GWT-Ext with SmartGwt there's hell lot of work anticipated. Its like working from the scratch.
So please do share all the info if you have been successful in migrating the GWT from 1.7 to 2.7.

Regards,
Nandita

On Thursday, December 18, 2014 at 6:08:47 PM UTC+5:30, ssg wrote:

Jens,
Extremely sorry for multiple postings of same questions. Reason for this is I did not find my earlier postings. A BIG thank you for  answering my questions. I will start working towards implementing your suggestions. I will get back to you soon. Thanks a lot once again.

On Wednesday, December 17, 2014 5:55:23 PM UTC-5, Jens wrote:

As I am new to GWT & development, I have done the following based on current App gwt1.7.0
1) I have downloaded standalone GWT SDK 2.7.0
2) Current build.xml file using HostedMode as follows
    <target name="hosted" depends="javac" description="Run hosted mode">
    <java failonerror="true" fork="true" classname="com.google.gwt.dev.HostedMode">
Should I change the above lines to  SuperDevMode ?  

HostedMode does not exist anymore, so yes you would need to replace it. I guess your best bet is to execute webAppCreator of GWT 2.7.0 SDK and create a new sample project with it. Then compare the build.xml file of the sample project with the one of your app and make changes as needed.

 

3) Current App gwt 1.7.0 is using some GWT jar files under directory \WebContent\WEB-INF\lib. I have replaced these gwt jars (gwt-user, get-servlet,                gwt-servlet-deps) with the latest 2.7.0 jars.
     This directory also has jdom, jettison-1.0.1, json, gwtext & gwtextux jars. Do I have to replace all these with the latest jars or only the gwtext & gwtextux jars ?

In WebContent/WEB-INF/lib should never ever contain gwt-user.jar / gwt-dev.jar. Both jars are only used during development and compilation to JavaScript. Only gwt-servlet.jar / gwt-servlet-deps.jar need to be deployed on server side (if you use GWT-RPC).

It also seems strange that other GWT libraries (gwtext / gwtextux) are in WEB-INF/lib since you usually don't need GWT libraries on the server. But I don't know these libraries so maybe they contain server side classes as well.

I found gwtext-2.0.5 at http://gwt-ext.com/download/. Is this the latest and the right one for migrating to gwt 2.7.0 ?
I found gwtextux.jar at http://www.java2s.com/Code/Jar/CatalogJar.htm

No idea if all your libraries are compatible to GWT 2.7, you need to check that on your own.

 

In the above code I  have modified/changed the first line FROM
<!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 1.7.0//EN" "http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd"> 
         TO
<!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 2.7.0//EN" "https://gwt.googlesource.com/gwt/+/2.7.0/distro-source/core/src/gwt-module.dtd">
Is this modification correct?

Replace

https://gwt.googlesource.com/gwt/+/2.7.0/distro-source/core/src/gwt-module.dtd

with

http://www.gwtproject.org/doctype/2.7.0/gwt-module.dtd

Is there anymore changes I need to do in this xxxxx.gwt.xml file ?

The <script> tags in your *.gwt.xml file will cause a compile error in GWT 2.7 because by default GWT 2.7 uses a new linker that does not support these <script> tags. You need to include these scripts directly into your host page or use the class ScriptInjector + ClientBundle/TextResource to inject them when your app starts. 

-- J.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.