Community
Participate
Working Groups
Build Identifier: Could be 1.4.4 or 3.6.2. There are dozens of eclipse parts in RD/z Customer name = BNP PARIBAS ITAM department customer number = 0772047 PMR = 15204,660,706 RTC SRR number = 44213 Reproducible: Always Steps to Reproduce: 1. In RD/z 8.0.2, click Window / Show view / Other / General 2. Click Internal Web Browser 3. Type this URL http://www-03.ibm.com/services/supline/products/java.html or any web page that has a java applet. 4. The web page appears but the java applet within it does not.
I presume the applet loads properly in Internet Explorer, correct?
Yes that is correct the web page with the applet loads correctly in both Internet Explorer and Mozilla web browsers when launched externally. The problem happens only in the case of launching an Internal Web Browser in Eclipse.
Are _all_ of the conditions in the "Windows" section of http://www.eclipse.org/swt/faq.php#browserapplets being met? This is the only context in which applets are expected to work with IE-based Browsers.
Yes I think all conditions are respected (IE 8.0, XULRunner version 1.9.2, JRE 1.6.0_31, updated JRE's boot classpath) but the applet still does not appear.
(In reply to jean-marc vince from comment #4) > Yes I think all conditions are respected (IE 8.0, XULRunner version 1.9.2, > JRE 1.6.0_31, updated JRE's boot classpath) but the applet still does not > appear. Hello. I have exactly the same problem and I think everything in requirement list is met. My configuration is: - Eclipse Juno RCP distribution (x86) - Windows 7 (x64) - JRE1.7 Update45 (x86) - IE9 (x86) Have you already find the solution or is there anybody who can run applets in internall browser on Windows 7/default IE? I use site: http://java.com/en/download/installed.jsp to check version of the Java, which shows java is undetected. Thank you for any hint
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
