On Friday, January 31, 2014 3:35:19 PM UTC-5, Thad Humphries wrote:
Thank, Jens. That's working: I added "-Dgwt.codeserver.port=9876" to the 'VM Arguments' in my run configuration and my RPC call works.I'm guessing there might be similar magic when running -noserver, right? I want to tackle that next, since Jetty configuration is gone with 2.6.0 and I dearly miss being able to configure my log4j.properties beyond my product's default.
On Friday, January 31, 2014 3:11:57 PM UTC-5, Jens wrote:When using SuperDevMode your server side code must access the GWT-RPC serialization policy files from your SDM code server (because thats the one compiling your app and generating the up-to-date policy file).This was kind of annoying with previous GWT versions but now GWT is able to download these files from the code server automatically if you set the system property gwt.codeserver.port for your server. As you seem to use classic DevMode as jetty server you must launch classic DevMode with -Dgwt.codeserver.port=<your SDM code server port>If for whatever reasons your SDM code server is not listening on localhost you have to override RemoteServiceServlet.
getCodeServerPolicyUrl(). Also take a look at the JavaDoc of that method.-- J.
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 firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.