Man, I know the frustration you're talking about. :) I don't know if your problem stems from the applet config information in your HTML (template) or not but if it does this may help...
<table border="0" cellspacing="0" cellpadding="0"> <tr><td> <OBJECT classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93" WIDTH=420 HEIGHT=400 NAME="EnrollmentTree" codebase="http://java.sun.com/products/plugin/autodl/jinstall-1_4_0-win.cab# Version=1,4,0,0"> <PARAM NAME = CODE VALUE = "SelectApp.class" > <PARAM NAME = CODEBASE VALUE = "$content.getURI("applet/")" > <PARAM NAME = ARCHIVE VALUE = "p_v1.jar" > <PARAM NAME = MAYSCRIPT VALUE = true > <PARAM NAME="type" VALUE="application/x-java-applet;jpi-version=1.4"> <PARAM NAME="scriptable" VALUE="true"> <COMMENT> <EMBED type='application/x-java-applet;jpi-version=1.4' width='420' height='400' pluginspage='http://java.sun.com/products/plugin/index.html#download' java_code='SelectApp.class' java_codebase='$content.getURI("applet/")' archive='p_v1.jar' name='EnrollmentTree' MAYSCRIPT='TRUE' > <NOEMBED> </COMMENT> This applet won't run in your browser. </NOEMBED></EMBED> </OBJECT> </td></tr> </table> I'm still using Turbine 2.1 (it works!) but I find it hard to believe that a later version of Turbine is going to break this. My Java runtime version is 1.4.1. I've only tested this with IE 5.5 and 6. My applet code is in a directory "applet" in the root of the web app. That directory contains my main applet class SelectApp and a jar file "p_v1.jar" that contains third party libs used by the applet. I haven't looked at this for a while so I can't remember how I got all this but it works. Hope it does for you, too. Blair Martin ----- Original Message ----- From: "David Ramsey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 19, 2003 1:58 PM Subject: Using Java applets in a Turbine/Velocity webapp > I come from the application programming world. While at Apple, I was > the author of MacPaint 2.0; I wrote a TV-in-your-computer application > for the long-defunct Aapps Corp., and I spent 9 years working on > various Mac and Windows interations of OmniPage at Caere/ScanSoft, > before they discovered that programmers in the Ukraine were a lot > cheaper than programmers over here. > > So I'm used to controlling every pixel on the screen and having dynamic > displays of information and although I've been doing webapps the last 3 > years or so, it's been a constant, background irritation that I was so > much at the mercy of the limitations (and capricious interpretations > thereof) of HTML. > > And now I've got a situation where a user can start a rather lengthy > process and I'd really, really like to display some real-time > information about the progress of said process, without requiring the > user to hit "refresh" or doing something lame like having the browser > page auto-reload every 5 seconds. > > The solution seemed obvious: use an applet. And wow, look, applets are > pretty easy to write, and I'm not sure how I'll hit the database yet > but hey, let's just get something going quickly here and see how it > works and start designing all that chewy user interface goodness with a > chocolate center. > > The more experienced Turbine users out there are already starting to > snicker, I know. > > Over the past couple of days I've been going slowly insane trying to > figure out how to use a Java applet in my Turbine/Velocity web > application. In most browsers, the area for the Java applet is blank, > generally with a red "X" or other indication of failure. A couple of > browsers display an error message about a "bad magic number." > > Searching the archives, I see this question has been asked several > times before. Responses fall into three categories: > > * No response at all-- this is the most common. This is disheartening. > > * A suggestion that the error message indicates that the applet class > or jar file is corrupted. > > * A sarcastic comment that this mailing list is for Turbine and not > client-side stuff like applets. > > Well, the applet file isn't corrupted; it works fine in a simple > hand-coded HTML page. Furthermore, the "bad magic number" error message > seems to be pretty generic: I can change any attribute of <applet> to > a random string, and get the _same message_. And I used to complain > about Mac OS error numbers, can you believe it? > > Because I have faith, I refuse to believe (admittedly in the face of > mounting evidence) that it's _impossible_ to use applets in a > Turbine/Velocity application. If I hadn't methodically tried almost > every directory in the webapp hierarchy, I'd think it was simply a > matter of putting the applet files in the right place. > > But damned if I can figure out what it is. > > Somebody out there must have done this. Or know how to do this. > > > > --------------------------------------------------------------------- > 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]
