Code changes not reflected on browser refresh

[Andrew]

Hi-

I'm using Eclipse 3.5.2 under Ubuntu with Google Web Toolkit SDK
2.2.0, and Google App Engine Java SDK 1.4.2.

Recently I worked through the StockWatcher example, found at
http://code.google.com/webtoolkit/tools/gwtdesigner/tutorials/stockwatcher.html

It used to work such that I could make changes to the java code in the
project (for example, in StockWatcher.java) while the development
server was running, then refresh my browser (pointed to http://localhost:8888),
and the changes in my code would immediately be reflected on the page.

However, something has changed. I have no idea what, or why. Now, if I
refresh my browser the code changes are not reflected on the page that
comes up. I have to recompile the entire project by clicking on the
red "G" icon labeled "GWT Compile Project" in the toolbar, which takes
a long time, then restart the development server, in order for my
changes to become visible in the browser (upon refresh). This is true
for both Firefox and Chrome.

I've tried a bunch of things to fix this... Project->Build
Automatically is checked, and I even tried reinstalling the GWT plugin
for eclipse.

If I make a change to an HTML file instead., for example
StockWatcher.html, the changes are reflected in the browser upon
refresh, as normal.

Please help! Recompiling the entire project every time is very
annoying.
Thanks.
Andrew

[Chris Conroy]

You need to point your browser at http://localhost:8888?gwt.codesvr=127.0.0.1:9997 (assuming you are running with the default settings). This URL also shows up in the DevMode tab when it starts up in Eclipse for you to copy paste or launch your browser.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Andrew Pikler]

Thank you! This fixed it.

I had been using that URL in the past, which is why I said it used to work... but for one reason or another, I switched to using just http://localhost:8888 for another app where that URL worked, and didn't realize I had to go back to the long URL for this one.