His,

I have been struggling with
com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException
(which finds several entries in web)
for a while and was able to find a clumsy workaround. Could anyone
please suggest a solution  in the following case as I believe it may
be either my configuration error or gwt bug.

Here is a sample project structure to refer to:
- java
- modules
| -- gwtclient

There is an ant task that compiles gwt code and puts it generated code
under modules/gwtclient, this folder is than zipped as war file and
deployed to jboss. It all runs then smoothly in a browser.

However should I start DevMode with "-noserver" option and the "-war"
option pointing at NOT PACKAGED directory modules/gwtclient in the
project structure, the following exception
"com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException:
Type 'XYZ' was not assignable to
'com.google.gwt.user.client.rpc.IsSerializable' and did not have a
custom field serializer. For security purposes, this type will not be
deserialized."
will be thrown.
I noticed that on every start DevMode creates new .gwt.rpc file under
modules/gwtclient (and not to deployed war) and that the exception
disappears if the modules/gwtclient is packaged and redeployed as
DevMode runs.

>From 
>http://groups.google.com/group/google-web-toolkit/browse_thread/thread/d026ef687c504eef#
I understand that the server (jboss' tomcat?) cannot find
suitable .gwt.rpc file and falls back to LegacySerializationPolicy
which demands IsSerializable interface.

Shouldn't DevMode running with -noserver argument be able create
new .gwt.prc files direct in the war file deployed to jboss or not
create it at all?
Is this a bug or my DevMode configuration mistake?

Thanks
-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.


Reply via email to