Fellas, After further research, I discovered a very tricky and hard to detect bug: I forgot the damn entry point in my .gwt.xml
Otherwise, everything is working really well. Thanks for all your help Jens! As a related question, Is there any way to debug SDM and AppEngine server at the same time?? Thanks, E On Tuesday, November 10, 2015 at 2:33:25 PM UTC-5, Evan Ruff wrote: > > Hey Jens, > > Thanks for all the advice. I think I'm getting close, but I'm still not > quite there yet. > > I added -noserver and -war path/to/my/exploded/war to my dev options for > the SDM configuration. > > Now, I start SDM, then I start AppEngine and I've got: > http://localhost:8080 (AppEngine server, looks good) > http://127.0.0.1:9876 (SDM Code Server) > http://localhost:9876 (recompile-requester?) > > When I browse to my index page the "Compiling Application" thing comes up > as expected so I think all of my files are making it into the war; however, > I'm still not getting my entry point to come up. Further, when inspecting > everything in Chrome Dev Tools, the only sourcemapped code I can find is > com/google/gwt and gen/com/google/gwt, no notice of my code anywhere. > > app.nocache.js seems to load as expected. I'm not getting any errors in > the console. Everything in the the network frame seems to load and I even > get one of the .cache.js files. Just not the entry point running! > > Am I missing something in my artifact or related to get my GWT code in the > build? When I look in the exploded war, my /app directory is in there with > a bunch of 60kb *.cache.js files, which feels about right for the current > functionality. > > The entry point doesn't ever seem to run. I'm wondering what else could be > going on in my config. Does anyone have any other ideas about what to check? > > Thanks! > > E > > On Mon, Nov 9, 2015 at 7:58 PM, Jens <[email protected] <javascript:>> > wrote: > >> >> 1. If I'm using AppEngine and SDM, do I need to have to separate debug >>> configurations? One for SDM and one for AppEngine? Then start them one >>> after the other? >>> >> >> Never used AppEngine but I would generally say yes since you most likely >> launch SDM with -noserver when using AppEngine server right? >> >> >> >> >>> 2. At this point, I can get to /_ah/admin and I can get to the >>> "Compiling..." screen of SDM. It looks like everything compiles correctly, >>> but when it tries to actually load my entry point, nothing happens. There's >>> no source map for my code in Chrome, only the standard library stuff. Also, >>> when I look in the log I see: >>> >>> Running Codeserver at ... >>> /home/gte619n/.IntelliJIdea15/system/gwt/cms.75073451/cms.9605c5e5/run/www >>> >> >> Thats the default if you do not pass -war /path/to/exploded/war as dev >> mode parameter in your run configuration. >> >> >> >>> But then working dir /tmp/gwt-codeserver-2976851721674933708.tmp >>> >> >> Thats the SDM CodeServer working directory. Not important for you. >> >> >> >>> But then I see that after compiling it says: Linking into >>> /tmp/gwt-codeserver-2976851721674933708.tmp/com.hs.auto.app.Application/compile-2/war/app >>> >> >> Just a sub directory of your SDM work directory. Everytime your recompile >> your app in the browser a new compile-1, compile-2, ..., compile-n folder >> will be created. Thats normal and not really important for you. >> >> >> How should I configure this correctly? >>> >> >> Probably depends if you want to run everything through Gradle or through >> your IDE. I usually launch things through my IDE so what I do is: >> >> 1.) Goto Project structure and create exploded war artifact (might >> already exist because of gradle) for all the server stuff >> 2.) update GWT run configuration and add -war >> /path/to/exploded_war_artifact/ >> 3.) create a server (in my case jetty) in IntelliJ and tell it to deploy >> the artifact created in 1.) >> >> Then I start SDM through the run config, then Jetty through its run >> config (which then deploys the artifact of 1.) which should contain GWT >> related stuff because of 2.)). >> >> >> -- J. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "GWT Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/google-web-toolkit/dG-vWxarXw4/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/google-web-toolkit. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
