Heyo,

It seems that I encountered a strange behaviour but before I start here the 
prerequisites:

GWT 2.4.0
Maven 3.0.3
gwt-maven-plugin 2.4.0
eclipse Kepler Service Release 1
GPE 3.4.2.v201310081834-rel-r43

The application is hosted in an external tomcat and I'm trying to debug.
If I'm debugging with mvn gwt:debug and launching a Remote debugging 
configuration from within eclipse I'm able
to debug properly. The serialization policy choosen is known to the server 
and therefore everything is ok.

If I'm trying to start as a web application from within eclipse, same 
configuration, same main class, same war folder and from my perspective
the same GWT version (though it could be possible that in this case the 
embedded SDK is used). The application chooses
for whatever reason a serialization policy (which it generates on the fly) 
which is unknown to the server and therefore RPC doesn't work.

Any ideas what could cause this issue?
Would be great to start directly from within eclipse to be able to use Hot 
Code replacement with transitive project dependencies.

Greetings!

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to