Thanks Rajeev.

I've raised http://code.google.com/p/googleappengine/issues/detail?id=3389

Setting the proxy properties did work. I hadn't tried that because i
had presumed it used the network access mechanism specified in
com.google.appengine.api.urlfetch.dev.LocalURLFetchService, which
doesn't pay attention to proxy properties.

It would be great if that could be fixed to. I have a patch for it
attached to the issue: 
http://code.google.com/p/googleappengine/issues/detail?id=544,
and applying it would make upgrading much easier.

(Yes, being behind a proxy is annoying)


On Jun 23, 12:24 am, Rajeev Dayal <[email protected]> wrote:
> Can you file an issue for this (passing DevAppServer arguments when running
> with GWT)?
>
> As for a workaround, can you try adding the following JVM arguments to your
> launch configuration:
>
> -Dhttp.proxyHost=<http proxy hostname> -Dhttp.proxyPort=<http proxy port>
> -Dhttps.proxyHost=<https proxy hostname> -Dhttps.proxyPort=<https proxy
> hostname>
>
> On Wed, Jun 16, 2010 at 1:07 AM, Nick Lothian <[email protected]>wrote:
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Reply via email to