View Full Version : GXT 1.0.2 and GWT 1.5.2
tbuckel
1 Sep 2008, 11:43 PM
Hi all,
we've just switched to GWT 1.5.2 and are now receiving a warning from the GWT compiler about a Serialization issue:
Analyzing the fields of type 'com.extjs.gxt.ui.client.data.BaseModelData' that qualify for serialization
protected com.extjs.gxt.ui.client.data.RpcMap map
com.extjs.gxt.ui.client.data.RpcMap
Verifying instantiability com.extjs.gxt.ui.client.data.RpcMap
Analyzing the fields of type 'com.extjs.gxt.ui.client.data.RpcMap' that qualify for serialization
private java.util.Map<java.lang.String, java.lang.String> _map
java.util.Map<java.lang.String, java.lang.String>
Verifying instantiability
com.google.gwt.i18n.client.impl.ConstantMap
Analyzing the fields of type 'com.google.gwt.i18n.client.impl.ConstantMap' that qualify for serialization
[WARN] Field 'private final com.google.gwt.i18n.client.impl.ConstantMap.OrderedConstantSet<java.lang.String> keys' will not be serialized because it is final
It seems that the new compiler version picks up the field RpcMap.map which is HashMap<String, String>, then searches for all classes extending HashMap<String, String> and find's GWT's own ConstantMap...
Though the code still works, it would be very good to have a way to get rid of this warning.
Cheers,
Thomas
eugenparaschiv
2 Sep 2008, 1:36 AM
GWT 1.5.2 comes with a few changes. Some functionality that used to work without any warnings or errors now gets errors. For example, when passing the mouse over the cells of a table (which is a common thing to do obviously). Let's just be glad the code works, and if you want to get rid of your warnings, simply run GWT with the debug levels set to Errors.
tbuckel
2 Sep 2008, 5:12 PM
Well, ignoring the compiler warnings isn't usually the preferred solution...
What are your experiences with GWT1.5.2 so far? You mentioned errors...
eugenparaschiv
2 Sep 2008, 11:14 PM
Hy. I'm experiencing problems with the table. Each time I go with the cursor over a table cell, there is a weird error. Not a warning mind you, but an actual error.
Grandiosa
3 Sep 2008, 12:10 AM
I get the same warning on the Map<String,String> , but my tables are working fine after the upgrade.
alex.d
3 Sep 2008, 4:56 AM
Having same problem with table-cells/rows. Going with the mouse over them causes an UncaughtException. Not a dealbreaker, but i'd gonna wait till GXT has fixed this bug before i switch to GWT 1.5.2.
gicappa
5 Sep 2008, 2:21 AM
I have got the same warnings also upgrading to GWT1.5.2 and GXT1.0.4. Does this happens also to someone else? Is there a way to fix it? I don't have any other error but, as you said I don't like to ignore warnings.
alex.d
5 Sep 2008, 2:46 AM
Same with me. Version 1.0.4 - bug is still there. Current "bugfree" zone - GWT 1.5.1 and GXT 1.0.2.
Having same problem with table-cells/rows. Going with the mouse over them causes an UncaughtException. Not a dealbreaker, but i'd gonna wait till GXT has fixed this bug before i switch to GWT 1.5.2.
Same problem here. There is NullpointerException on cell mouse over with GWT 1.5.2 + GXT 1.0.4. Same code works with GWT 1.5 + GXT 1.0.3.
paulsschwarz
15 Sep 2008, 9:44 AM
Hi guys, I'm not sure if this is still the debate but please check out this thread and specifically look at the comment from Miguel Mendez
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/4d38cff6b1c217c6
<set-property name="gwt.suppressNonStaticFinalFieldWarnings" value="true" />
If you read the release notes of GWT 1.5.2 you'll see this:
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.
I'm not sure if I totally know what I'm talking about but I think the answer is this:
All along in 1.5.x we were supposed to be recieving this warning but in 1.5.2 they turned it on.
The quick fix is
<set-property name="gwt.suppressNonStaticFinalFieldWarnings" value="true" />
The real fix is for GXT to go into their implementation and put the transient keyword in the right places.Cheers
alex.d
15 Sep 2008, 11:12 PM
Thx paulsschwarz,
interesting info. At least now we have a workaround. But it would be really nice if someone from the developer team (is there a team, Darell?) could say smth. like "we are looking into it - should be fixed any time soon..." :-?
tbuckel
15 Sep 2008, 11:37 PM
Thanks all.
Fully agree with alex.d - any kind of feedback from the GXT dev team (Darrell) would be appreciated.
Otherwise - IMHO - we should question the licensing and support model of GXT.
alex.d
17 Sep 2008, 11:55 PM
GWT 1.1 is out - can anyone confirm, whether the bug is still there?:-?
still there as for the samples that come with gxt.
Daniel Kurka
30 Sep 2008, 8:14 PM
Hi Alex,
I posted a bug request in the premium help forums concerning this issue and its fixed now.
Having same problem with table-cells/rows. Going with the mouse over them causes an UncaughtException. Not a dealbreaker, but i'd gonna wait till GXT has fixed this bug before i switch to GWT 1.5.2.
alex.d
5 Oct 2008, 10:37 PM
Thx mister Premium Member ;)
tbuckel
5 Oct 2008, 11:05 PM
well done!
walkerr
10 Oct 2008, 2:50 AM
We're getting this too - and we're not a GXT user.
I think you may find it's an underlying GWT 1.5.2 issue:
http://code.google.com/p/google-web-toolkit/issues/detail?id=2862
Seems like GWT re-enabled the warning, but they have an instance of it in their own codebase that triggers it.
FWIW - we elected not to disable the warning, the risk being we miss a case of this in our own code with more fatal results
jraue
20 Oct 2008, 4:02 AM
Thanks for the info, Paul. However, I believe it is not up to the GXT team to add a transient, but to the GWT team, since the warning comes from com.google.gwt.i18n.client.impl.ConstantMap.OrderedConstantSet<java.lang.String> (this is what I see at least).
The problem in GWTs OrderedConstantSet persists in GWT 1.5.3.
walkerr
20 Oct 2008, 5:01 AM
I don't think I was implying it was up to the GXT team to make any changes - in fact quite the opposite. By including the link I was passing on the information that this *is* a recognised GWT bug rather than anything in GXT.
jraue
20 Oct 2008, 5:05 AM
Sorry for the confusion, I was referring to paulsschwarz post on page 1.
walkerr
20 Oct 2008, 5:08 AM
Aha - no problem then. I agree with you - it's not a task for GXT to try and fix ;)
Powered by vBulletin® Version 4.1.5 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.