It sound like your GWT code server launcher directory setting isn't correct. And it doesn't look correct either. It should be the war directory of your project.
So, something like "c:\whereever_your_code_is\your_project\war" (you might not have called it "war", it's called whatever you put in the settings in GWT -> Web Application -> WAR directory). Basically, the GWT code server needs to override the (your_module).nocache.js file, so it need to know where that is, and that is in a directory under your war directory. On Friday, 18 March 2022 at 9:59:04 am UTC+11 [email protected] wrote: > Hello, > > Recently, I started to resume on our GWT upgrade project with GWT 2.9 and > JDK 11. > > As it has been discussed before, the embedded Jetty server can't work with > JDK 11 due to the ASM lib version issue. The recommended approach is to set > up an external server, so I followed the following GWT document to manually > configure GWT development mode by following steps specified in the second > Video. I've watched the video and tried this approach many times, but it > still gave 404 error. It seems hard to setup external server and configure > Development mode correctly for our project. > > Any input or suggestion is greatly appreciated! > > *http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html > > <http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html>* > > Manually Configure GWT Development Mode > > Manually Configuring the -launcherDir in the GWT Eclipse Plugin > > Our GWT project is not Maven oriented and it was developed several years > ago with a big codebase. > > Step 1: Converted Aries project to Dynamic Web Project by adding project > facet "Dynamic Web Module" in Eclipse. > > Step 2: Set up Apache Tomcat 9 Server > > Step 3: Add the project to server. Right click on Server -> Add and Remove > > Step 4: Start the Tomcat Server > > Step 5: Right click project->Debug As -> GWT Development mode > > Step 6. It started fine. Stop it so we can add the -launcherDir Program Arg > > Step 7: Double click on Tomcat server, select Open launch configuration > > Get the server web app directory root: wtp.deploy > > Copy path > > > C:\EclipseGWTCodeServerWorkSpace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps > > Step 8. Open the file explorer to see the deployment path > > Step 9: Go to Debug Configurations > > GWT Development Mode (CodeServer)->Arguments. > > Add -launcherDir > > Value: It is the wtp.deploy arg + context path. > > After updated the Argument to GWT Development Mode(CodeServer), the > Arguments tab has following content: > > -launcherDir > C:\EclipseGWTCodeServerWorkSpace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\aries > > -logLevel INFO -port 9876 edu.vanderbilt.mc.aries.ARIES > > Step 10 Launch the code server, click on Debug from CodeServer dialog. Now > both the Web Server and Code Server are running. Back to the file manager. > Watching for the application directory to be created. > > Step 11: Launch the browser for debugging with the Javascript Debugging > > Open with SBDG debugger > > Step 12: Open browser with Code Server URL: 127.0.0.1:9876 and Change the > port number to 8080 ( the Tomcat web server port number) > > It gave me 404 Not found error. > > Your help is greatly appreciated, > > Jenny > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/77678bff-1531-4891-a6b0-8b6aac57e009n%40googlegroups.com.
