Microsoft KB Archive/177750

= Visual J++ relaxes security restrictions on Java applets =

Article ID: 177750

Article Last Modified on 6/14/2006

-

APPLIES TO


 * Microsoft Software Development Kit for Java 2.02
 * Microsoft Software Development Kit for Java 3.0
 * Microsoft Software Development Kit for Java 3.1
 * Microsoft Software Development Kit for Java 3.2
 * Microsoft Visual J++ 1.0 Standard Edition
 * Microsoft Visual J++ 1.1 Standard Edition

-



This article was previously published under Q177750



SUMMARY
How does the Msdev.exe, in Visual J++, relax the security in Internet Explorer so that my applet can run outside the Java sandbox, despite the fact that it is not in a signed .cab file?



MORE INFORMATION
In the Microsoft virtual machine, which is included with Internet Explorer 3.x and 4.0x, only trusted class files can access resources outside the Java sandbox. Class files from digitally signed .cab files are trusted. If the HTML file is run from Microsoft Developer Studio, the class files are also trusted. This can be very helpful during applet development. However, to deliver your applet to other users, you must place them in a signed .cab file.

When executing or debugging a Java Applet from Developer Studio, the security restrictions in Internet Explorer are relaxed for quick and easy testing. MSDEV prepends the project path to the CLASSPATH that is used by Internet Explorer. This gives the classes trusted status.

Applets outside of MSDEV must be cabbed and signed in order to run in Internet Explorer without the sandbox restrictions. One of the references below is an FAQ about cabbing and signing.

NOTE: All trusted applets (including those running under Developer Studio) running under the Microsoft virtual machine (version 2252 or higher) included with either the SDK 2.0x for Java or Internet Explorer 4.0x have additional restrictions (please see references below).

