Re: dev mode: fallback to 1.3.3 serialization after making a change

2013-10-15 Thread Jens
I don't think so. You can customize the way the server looks up that file in RemoteServiceServlet.doGetSerializationPolicy() and technically you could download that file from an URL that points back to your developer machine. Maybe that can help you. But normally you want that modified code on

Re: dev mode: fallback to 1.3.3 serialization after making a change

2013-10-15 Thread Dennis Haupt
can this be avoided somehow? it also happend when i make a change that really shouldn't break serialization (change code, but no fields) 2013/10/15 Jens > First reload DevMode / Recompile app, then deploy to server (or tell the > server to reload the exploded war directory if you use a local se

Re: dev mode: fallback to 1.3.3 serialization after making a change

2013-10-15 Thread Jens
First reload DevMode / Recompile app, then deploy to server (or tell the server to reload the exploded war directory if you use a local server). Whenever you make a change to a serializable class that is used in a GWT-RPC service the .rpc file for that service will be updated and thus gets a n

dev mode: fallback to 1.3.3 serialization after making a change

2013-10-15 Thread Dennis Haupt
what can cause this (the hashcode-rpc-file is not found), and how can i fix it? this problem forces me to restart my server and rebuild my gwt module a lot -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and