View Full Version : migration to ExtGWT from myGWT 0.5.2

14 May 2008, 1:02 PM
Our company is planning to migrate to ExtGWT from myGWT. Our application is currently developed in 0.5.2.

I would like to know whether migrating to ExtGWT would resolve the following error that occurs in case of IE in our current application. But this error does not happen in firefox. Only in IE 7.0 after 8 clicks with in our application this exception occurs which is consistantly reproducible. Firefox does not give this exception even after 8 clicks.

Exception stack trace:
com.google.gwt.core.client.JavaScriptException: JavaScript Error exception: Unexpected call to method or property access.

at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:481)
at com.google.gwt.dev.shell.ModuleSpace.invokeNativeVoid(ModuleSpace.java:270)
at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid(JavaScriptHost.java:137)
at net.mygwt.ui.client.util.CSS.setRules(CSS.java:57)
at net.mygwt.ui.client.util.StyleTemplate.apply(StyleTemplate.java:54)
at net.mygwt.ui.client.widget.table.Table.onRender(Table.java:710)
at net.mygwt.ui.client.widget.Component.render(Component.java:1140)
at net.mygwt.ui.client.widget.Component.getElement(Component.java:431)
at net.mygwt.ui.client.widget.Layout.renderAll(Layout.java:74)
at net.mygwt.ui.client.widget.Layout.onLayout(Layout.java:66)
at net.mygwt.ui.client.widget.layout.FillLayout.onLayout(FillLayout.java:107)
at net.mygwt.ui.client.widget.Layout.layout(Layout.java:42)
at net.mygwt.ui.client.widget.WidgetContainer.onLayout(WidgetContainer.java:341)
at net.mygwt.ui.client.widget.WidgetContainer.layout(WidgetContainer.java:235)
at net.mygwt.ui.client.widget.WidgetContainer.layout(WidgetContainer.java:251)
at net.mygwt.ui.client.widget.WidgetContainer.onAttach(WidgetContainer.java:324)
at com.google.gwt.user.client.ui.Widget.setParent(Widget.java:241)
at com.google.gwt.user.client.ui.Panel.adopt(Panel.java:119)
at com.google.gwt.user.client.ui.HTMLTable.setWidget(HTMLTable.java:1100)


So, I am just wondering whether migrating to Ext GWT would resolve this issue.


14 May 2008, 2:08 PM
hard to say - how about you outline the problem and provide more details on what caused the event in the first place...

14 May 2008, 2:23 PM
at net.mygwt.ui.client.util.StyleTemplate.apply(Style Template.java:54)
at net.mygwt.ui.client.widget.table.Table.onRender(Ta ble.java:710)

With Ext GWT, Table no longer uses StyleTemplate and CSS which has know issues in IE after resizing and sorting several times.

14 May 2008, 2:35 PM
Thanks Darell. With that I can see that this issue will be resolved once I migrate my application to Ext GWT which has been a major issue in our application.

BTW, how easy it is to migrate from myGWT to ExtGWT? Because, I can see lot of API have changed. For example we use WidgetContainer in myGWT and it is Container in Ext GWT. Also BaseEvent has been changed etc., Do we manually change these APIs or do we have quick tools and tips that assist in migration?


14 May 2008, 3:29 PM
There are no tools for the upgrade. The best bet is to review the explorer demo code to see how the API now works. If you can wait a few days, I would recommend waiting for beta3 as there are some changes to the API from beta2. There should not be any changes to the API once beta3 is released unless they are absolutely needed.

14 May 2008, 3:39 PM
Thank you Darell. BTW, my application also is currently using GWT version 1.4.61. Does Ext GWT work with this version of GWT 1.4. I just wanted to confirm on this.


14 May 2008, 3:48 PM
Ext GWT only works with GWT 1.5 M2

I migrated my app and it was fairly straight forward - mostly conversion from old class/method to new class/method.

Approach stayed fairly much the same.

14 May 2008, 4:07 PM

We really do not want to upgrade to GWT 1.5 for a while. Can I just upgrade Ext GWT alone with any settings that can help make Ext GWT to work with GWT 1.4?

(Or) is it a must for Ext GWT.


14 May 2008, 4:09 PM
No, GWT 1.5 is required.

14 May 2008, 4:10 PM
I can't see how you can - The gxt.jar is compiled to Java 5.0 bytecode and the Ext GWT source uses a lot of Java 5 language improvements (like generics etc) and so you'll not be recompile either... I think you are possibly stuck !!

14 May 2008, 4:38 PM
Thank you. That helps.


14 May 2008, 5:33 PM

Is there any workaround with myGWT 0.5.2 to avoid this error until we mgirate to ExtGWT and GWT 1.5? Does commenting the following line in Table.java in myGWT 0.5.2 and recreating the jar avoid this error?


(or) could you please suggest other alternatives to avoid this error for a short term fix?

I would appreciate if you could suggest some short term fix until we migrate to ExtGWT as our application is reaching production in few days.