I also had some trouble working with a test for loading an applet. It seems like there may be some security exception if it is not traveling across the same port as the page that is calling the applet... I don't remember exactly what the security settings were, but I ended up putting the java class files in the main web server and calling from there to avoid the security issues.
hth! -- Regards, Jeffery Painter - -- [EMAIL PROTECTED] http://kiasoft.com PGP FP: 9CE8 83A2 33FA 32B1 0AB1 4E62 E4CB E4DA 5913 EFBC On Fri, 21 Nov 2003, David Ramsey wrote: > > On Nov 21, 2003, at 12:03 PM, Adam Greene wrote: > > > No, God doesn't hate anyone, Computers on the other hand... :-) > > > > What version of the Sun Plugin are you using or are you? What version > > of > > Netscape / IE are you using? What was the applet compiled with? > > 1.4.1_03. > > On OS X: Safari 1.1.1, IE 5.2.3 > On Win XP: 6.0.28000 > > On both platforms the applet is compiled with Code Warrior 8. Recall > said applet works perfectly when referenced from a stand-alone HTML > page. > > -- David > > > > > > > > > -----Original Message----- > > From: David Ramsey [mailto:[EMAIL PROTECTED] > > Sent: Friday, November 21, 2003 2:53 PM > > To: Turbine Users List > > Subject: Re: Using Java applets in a Turbine/Velocity webapp > > > > > > There must be something so amazingly basic I'm overlooking. No, your > > example does not work. I can easily build and run the clock applet in a > > separate HTML page. But it doesn't work when invoked from my webapp. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
