Hi all!
I tested this behavior the last days, and remarked that this generated
rpc file contains entries (as row) with all types that could be use
during rpc call, all with false after it. It's not possible to set
it back to true, since the gwt.rpc file is generated at any running.
Is there a
Hi all
i just spent more than a whole day on this issue. Do somebody why this
problem occurs?
I tried almost all solutions discussed on this thread. But nothing
seems to work.
here is my error message:
Type 'cm.bao.sms.ui.web.gwt.client.wrapper.BooleanWrapper' was not
included in the set of
For now I'm using the GWT compile button of the eclipse plugin to
force a proper GWT 2,0 compile. This seems to work for me.
The problem must be that some older GWT compiler is been executed
somehow.
Alex
On Dec 14, 3:17 pm, Addy adityaka...@gmail.com wrote:
I cleanup after every build but
I cleanup after every build but since converting to 2.0, I started
encountering intermittent Serialization exceptions even in production.
I had to switch back 1.7.
For production use, cleaning up browser cache is not an option as I
cant tell all my users to do so.
I guess I will have to wait a bit
When a new version comes these are the standard steps to do:
1 - put the jars
2 - perform a full rebuild of the application
3 - clean up the browser cache
4 - clean up the temp folder, where the GWT is generating the
compilation crap...
5 - run the application :-))
Cheers,
Sorinel CRISTESCU
--
Yup, Ive got the same problem having just upgraded to 2.0.. G
On Dec 12, 12:27 am, Dop Sun dop...@gmail.com wrote:
While I upgraded my project settings to 2.0 (via Google Eclipse
Plugin), and have a runtime error while running in development mode:
Actually, sorry, not sure ive got the SAME problem, I have:
com.google.gwt.user.client.rpc.SerializationException: Type
'com.ideba.net.client.LoginInfo' was not assignable to
'com.google.gwt.user.client.rpc.IsSerializable' and did not have a
custom field serializer.For security purposes, this
Thx John:
The way I fixed it is a little bit different:
I deleted all files generated by old compiler, and then, the problem
disappeared. I guess, the problem is because the new compiler is
different from the new compiler.
Cheers.
Dop
On Dec 13, 4:47 am, John V Denley johnvden...@googlemail.com
I am losing my mind... I just upgraded to GWT 2.0 on OSX 10.5 using
Eclipse 3.5 App Engine SDK 1.2.8 and previously working server calls
are now not working. When the application starts it grabs some data
from the server and this is still working. When I try to have a user
login I get the
@Dop Sun
Could you tell me which files were/are created by the old compiler? I
have tried cleanign and refreshing a bunch of stuff but maybe I am
missing something.
Thanx.
On Dec 12, 5:12 pm, Dop Sun dop...@gmail.com wrote:
Thx John:
The way I fixed it is a little bit different:
I deleted
I have the same error in Hosted Mode. Production is fine. Making all
my types implement IsSerializable fixes the problem, but I'd really
rather not have to tie all my objects to GWT like that.
P.S: Maybe unrelated, I get this warning with the IsSerializable fix.
I'm getting multiple .rpc files in
While I upgraded my project settings to 2.0 (via Google Eclipse
Plugin), and have a runtime error while running in development mode:
com.google.gwt.user.client.rpc.SerializationException: Type 'xxx' was
not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and
did not have a custom
12 matches
Mail list logo
