Problem with SWT Browser and IE7 [message #491563] |
Wed, 14 October 2009 23:59  |
Eclipse User |
|
|
|
Hello,
I have a problem with using the SWT browser that is really weird. My project involves building a RCP application which embeds a SWT browser in the UI. The application runs in a network environment that requires proxy access (configured using a pac script; no authentication required).
When I run the application in Eclipse from source, the application behaves as expected (the browser loads the URL specified) However, when I build the application and run it as standalone RCP application, the browser opens the IE "This program cannot display the webpage" page (res://ieframe.dll/dnserrordiagoff_webOC.htm#<my URL>)
I am running this under Windows XP, tried running the process as unrestricted, but no luck. The same web site works fine in Internet Explorer and when running inside Eclipse, so I don't think it's a network issue. I configured the proxy settings using the org.eclipse.core.net package, and in Java code I am able to connect to the server, but it seems like IE is not able to connect.
I am using Eclipse 3.4.
I checked and make sure the Eclipse version is the same between my Eclipse environment and standalone environment. It's running under the same JVM as well, with same configuration settings (e.g., Xmx, Xms).
Any advices? I have been stuck on this for a long time and I can't figure out what the difference could be between running the application in Eclipse vs running in my RCP app...
Thanks,
Adrian
|
|
|
Re: Problem with SWT Browser and IE7 [message #491942 is a reply to message #491563] |
Fri, 16 October 2009 11:54   |
Eclipse User |
|
|
|
Hi Adrian,
Though I've never used a pac script before, it's likely that your script is
not being found in the RCP case. Can you add a line to print "Hello!" to
your FindProxyForURL() implementation to prove/disprove this? A resource
not being found is usually the cause when a behaviour changes when run in a
different environment. I can't imagine embedded IE behaving any differently
otherwise in an eclipse context vs. an RCP one.
HTH,
Grant
<adrian.pang@sap.com> wrote in message
news:hb66n4$12k$1@build.eclipse.org...
> Hello,
>
> I have a problem with using the SWT browser that is really weird. My
project involves building a RCP application which embeds a SWT browser in
the UI. The application runs in a network environment that requires proxy
access (configured using a pac script; no authentication required).
>
> When I run the application in Eclipse from source, the application behaves
as expected (the browser loads the URL specified) However, when I build the
application and run it as standalone RCP application, the browser opens the
IE "This program cannot display the webpage" page
(res://ieframe.dll/dnserrordiagoff_webOC.htm#<my URL>)
>
> I am running this under Windows XP, tried running the process as
unrestricted, but no luck. The same web site works fine in Internet
Explorer and when running inside Eclipse, so I don't think it's a network
issue. I configured the proxy settings using the org.eclipse.core.net
package, and in Java code I am able to connect to the server, but it seems
like IE is not able to connect.
>
> I am using Eclipse 3.4.
>
> I checked and make sure the Eclipse version is the same between my Eclipse
environment and standalone environment. It's running under the same JVM as
well, with same configuration settings (e.g., Xmx, Xms).
>
> Any advices? I have been stuck on this for a long time and I can't figure
out what the difference could be between running the application in Eclipse
vs running in my RCP app...
>
> Thanks,
> Adrian
|
|
|
Re: Problem with SWT Browser and IE7 [message #491949 is a reply to message #491942] |
Fri, 16 October 2009 13:12  |
Eclipse User |
|
|
|
Hello,
If I debug into the proxy code, it seems like Eclipse is able to find the proxy correctly (it detected the right proxy to use and the port number). If I connect using java.net.URL, it works as expected. However, it's only the embedded IE that cannot open internet web sites.
I tried upgrading to IE 8, which has the same problem, but if I downgrade to IE 6, the problem goes away -- I would assume it's something broken in IE 7, but that doesn't explain why it works in debug mode.
Very confused...
Adrian
|
|
|
Powered by
FUDForum. Page generated in 0.13340 seconds