Thanks for the replies. Glad to know that about -whitelist, makes
Basically, I've just gone back to 1.5.2. I can work quite well with
this, being able to hit other ports while still on localhost (or even
better, modifying my hosts file so it looks like I'm coming from
whatever host I want). I'll probably build against 1.5.3 for a final
build to deploy, but for debugging locally, 1.5.2 is much more
efficient for me.
I haven't looked into the speed issues with -noserver, but I wouldn't
doubt that it's just something on my end causing the slowdown.
I haven't looked into the imagebundle issues, and don't plan to for
the foreseable future -- sorry, just don't have time this month to
debug imagebundles on 1.5.3 with -noserver.
P.S. Just as you have a -whitelist option, perhaps consider a '-
sophole host:port' option to allow this type of debugging locally
without having to go to the -noserver route.
On Oct 22, 9:25 pm, "Sumit Chandel" <sumitchan...@google.com
> Hi Brian,
> Hosted mode shouldn't be any slower running with the -noserver option as
> opposed to with the embedded Tomcat server. Is it possible that the server
> you're using is somehow carrying a larger load than just responding to your
> GWT application resource and other server-side requests?
> About the issues you're having with the ImageBundle, what problems are you
> experiencing? Are the images not showing up at all, or is hosted mode having
> a hard time locating the resources? In terms of steps you can follow to get
> up and running with hosted mode with the -noserver option, check out the FAQ
> below to make sure you've got everything setup correctly to use hosted mode
> with -noserver.
> Using hosted mode with the -noserver option:http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=goog.
> Hope that helps,
> -Sumit Chandel