I've been trying to do what I read here[1]. I am able to use the "gwt:run" goal to launch the app in development mode, make code changes in Eclipse, and then refresh the browser and see the code changes reflected. However when I try to use "gwt:debug" instead, my first attempt to hit the server causes the server to fail out with:
[ERROR] ERROR: transport error 202: handshake failed - received >GET / LeonidsEx< - excepted >JDWP-Handshake< ["transport.c",L41] [ERROR] JDWP exit error JVMTI_ERROR_NONE(0): could not connect, timeout or fatal error This may relate to the bug at [2], because my project is on Java 5, but when I change to Java 6 (which isn't an option for the end deployment) the request fails with a 503 instead. So that indicates to me that this can be fixed for Java 5. Has anyone seen this before or have a better knowledge of what's going on when my server's running with the "gwt:debug" goal and I try to hit it from the browser? I know there's some HTTP knowledge I'm lacking here. [1] http://groups.google.com/group/google-web-toolkit/msg/cbbf6292588041f8?hl=en [2] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6339385 -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
