Hi I had similar issue lately. Important thing is that after switching to xsiframe linker you have to compile your application and use it for starting sdm. This way your app.nocache.js file will be built by that newly set linker and sdm scripts will detect it. Without that step nocache.js file will be old (created by std linker) - hence the error.
Good thing after changing linker is cleaning the project (and also removing gwt-unitCache folder). Without doing it I had some compilation issues. Greg On Thursday, October 17, 2013 8:11:02 PM UTC+2, crojay78 wrote: > > Thanks for the reply, Yes I added it my app.gwt.xml > > Am Donnerstag, 17. Oktober 2013 19:43:13 UTC+2 schrieb crojay78: >> >> Hi, >> >> i followed a lot of threads at stackoverflow and here in this group >> concerning the super dev mode. But it still does not work on my side. I >> have a multi module maven gwt project and want to use super dev with it. >> >> Actually it works to start the codeserver with the mvn gwt:run-codeserver >> and I can see the output >> >> [INFO] >> [INFO] The code server is ready. >> [INFO] Next, visit: http://localhost:9876/ >> >> >> I started this page and bookmarked the links. After this I am starting my >> tomcat with eclipse wtp plugin where my application is running. Then I >> connect to this application my tomcat server. The app is available and >> works, but for my understanding it should be able to use there the dev on >> link. But this shows me only the message >> >> Can't find any GWT Modules on this page. >> >> >> Any idea what the problem is? >> >> Thanks >> > -- 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.
