My guess is that you are using a separate war directory in your external server, have copied all of your static content over (including the *.gwt.rpc files) to that war directory, and then changed something about the serializable models that you are passing across your RPC calls. Whenever these models change the generated .gwt.rpc files will have changed. Your server would be using one variation of the serialization policies and your client java debugging would be using a different one.
I can think of two options:
Option #2 is the one I go with when dealing with large complex systems that require an external server.
This was my thought as well but I am using the same war directory. However the classes that the system is complaining about are in a seperate maven module. I am wondering if there is something that Intellij does when running in complete dev mode that it doesn't when the noserver flag is set?
xsee, Is there anything special I have to do in order to make this happen.
Hmmm, I don't use IntelliJ so it's hard for me to speculate but I doubt it is doing anything that would be too different from what eclipse does in this scenario. I wonder if your external Jetty server is caching the serialization policies? I haven't used an external Jetty in awhile so I don't have any configuration files handy to reference.
Ok, thanks. I think it may be related to the compiler setup. I am investigating ;)