First, to say what does work, and to help anyone else doing the same thing I am.
I can run a GWT application where the server code interacts with my deployed and running Tomcat server. The documentation and docs available did not help much as so much of GWT and IntelliJ has changed. I had to add GWT as a top level module (the "new" for GWT under "src" is missing so the online demo is obsolete, by the way), hand-edit my web.xml and startup HTML using the GWT as a sample (which is fine), and to have the build directory of GWT inherit from my project so the server code there can get at the code in my Tomcat app, and so it gets deployed with the rest. I can set a breakpoint in my server code and hit it when I run the GWT UI. Nice!
Debugging the client GWT app does not work.
The originally generated GWT sample app worked out of the box but stopped when I integrated the server-side code. The GWT Run/Debug configuration refers to "Shell parameters" but in GWT 2.0.3 this has been replaced by "hosted mode" so there no longer is the notion of "-noserver". I did find this post:
I am guessing I will want to start my Tomcat app, then also run GWT debugging in the now-obsolete "-noserver" mode, so GWT will connect to the afore mentioned Tomcat.
What should I use, in the "GWT Configuration", for "VM Parameters" and "Shell Parameters"? Or is this approach wrong?
Is there a specific EAP release where this will be made more convenient?