> BTW, is accessing client's System.out in an applet legal?
No[1], not unless it is signed.
[1] <http://mindprod.com/jgloss/applet.html#RESTRICTIONS>

Signature
Andrew Thompson
http://www.PhySci.org/codes/ Web & IT Help
http://www.PhySci.org/ Open-source software suite
http://www.1point1C.org/ Science & Technology
http://www.LensEscapes.com/ Images that escape the mundane
Roland - 21 Jan 2005 11:02 GMT
>>BTW, is accessing client's System.out in an applet legal?
>
> No[1], not unless it is signed.
>
> [1] <http://mindprod.com/jgloss/applet.html#RESTRICTIONS>
I think that needs some further clarification.
In an unsigned applet you *can* print to System.out/System.err (using
System.out.println(), System.err.print(foo) etc.). The output will show
up in the Java console.
But you cannot change System.out/System.err to your own PrintStream.
Calling System.setOut(PrintStream) or System.setErr(PrintStream) in an
unsigned applet (with default security permissions) will throw a
security exception.

Signature
Regards,
Roland de Ruiter
___ ___
/__/ w_/ /__/
/ \ /_/ / \
I tried changing the code so that no components are instantiated in the
event listeners, this did not help.
Thanks for the insight? though.
Frank
> One of the top five worst practices for GUI programming:
> -Instantiating a component in an event listener.
[quoted text clipped - 3 lines]
> BTW, is accessing client's System.out in an applet legal? I'm
> not so sure about it.
RC - 20 Jan 2005 21:54 GMT
All System.out will go to Java console for Applets.
> I tried changing the code so that no components are instantiated in the
> event listeners, this did not help.
[quoted text clipped - 10 lines]
> > BTW, is accessing client's System.out in an applet legal? I'm
> > not so sure about it.