Hi, If you want to pick up changes to your server code while the development server is running, you need to deploy your application in exploded-war format to JBoss.
When you run GWT in -noserver mode, you should point your -war directory over to your JBoss server's deployment directory - that way, any files generated by GWT will be dumped into your running server's directory. Unfortunately, there is a bug in GWT's RPC system that will prevent the server from picking up changes to the RPC serialization policy file, even if you copy the modified serialization file into the running server's deployment directory: http://code.google.com/p/google-web-toolkit/issues/detail?id=4548 I'd recommend that you star this issue if you want it to be prioritized. Rajeev On Thu, Jan 14, 2010 at 12:38 PM, denis56 <denis.ergashb...@gmail.com>wrote: > 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 google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
