Thank you for your reply. Most illuminating. Maybe I should start reading about what I'm trying to do before I actually try...
Great article also. /Clundahl Den lördagen den 20:e april 2013 kl. 11:40:10 UTC+2 skrev Thomas Broyer: > > > On Saturday, April 20, 2013 7:38:17 AM UTC+2, Clundahl wrote: >> >> Hi >> >> I have a maven setup that runs gwt in superdev-mode. To run the >> application I have just gone to the file://.../debug.html page and that >> works fine... when just testing stuff that are executed on the client side. >> When trying to run rpc-calls I get the "Origin null is not allowed by >> Access-Control-Allow-Origin." not strange since the file is on the >> "file://" and the service is on the >> http://localhost:9876/Foo/rpc<http://localhost:9876/Kloss/rpc> url, >> i guess. >> > > No, the codeserver only serves the client-side code. > > >> >> The problem is that I cannot find/place where to find the debug.html on >> the server. I look in the "target\Foo-1.0-SNAPSHOT" ant there it is... but >> the server does not find it on >> http://localhost:9876/Foo/<http://localhost:9876/Kloss/rpc> >> debug.html >> >> Do I have to declare where the file is for the jetty-server? Or anything? >> > > The general setup is to have an HTTP server (generally a servlet > container) running side-by-side with the codeserver. > > In other words: SuperDevMode requires a working application, and *then*you > enable SuperDevMode on it to hijack the client code from the codeserver. > See http://blog.ltgt.net/how-does-gwts-super-dev-mode-work > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
