elizabeth.mezias@Eng 1998-02-05
A customer has reported this problem and I am able to reproduce symptoms when running the SwingSet demo on a Toshiba Tecra laptop with 32MB of memory. Applet behavior is not the same when the Swing jar files are stored with the HTML page on a server. In the SwingSet demo I have observed painting problems which can render the applet unusable. The Java Console also reports additional exceptions, especially security exceptions, when running the SwingSet applet without local jar files.

The only effect of local jar files should be to improve throughput and performance. This is not the case. Our client has found that their applet's JTextFields do not respond at times unless the jar files are local to the client machine. Storing the Swing jars locally is currently requirement for them to run their applets with Internet Explorer.


patrick.ong@Eng 1998-02-05
The following email shows the steps taken by Beth Mezias to reproduce
the problem with SwingSet on IE4:

> From beth@single Wed Feb 4 09:03:44 1998
> To: <richie@taller>

> The exact steps to reproduce the problem are to run the SwingSet from a
> web server (I am using javaweb) without the Swing jar files in your CLASSPATH.
> The jar files are specified in the archive tag and are found on the server
> alongside the swingset.jar.

Please specify which part of the above steps is not the right way to run
SwingSet on IE4 ? Is IE4 not expected to run SwingSet with remote Swing jars unless the JRE is replaced with one that comes from JavaSoft's JDK ?