Re: JAVA applet probelems
On Mar 21, 5:35 pm, "merrittr" <merri...@gmail.com> wrote:
not sure I understand the compiled classes are in the same directory
as the web page.
What compiled classes? Are you saying the 2 (?)
classes your were first mentioning? Or,
'a whole bunch of classes that includes..
com.adobe.acrobat.Viewer.class'?
Viewer class should *not* be in the same
directory as the HTML, but indeed (as a loose
class) a subdirectory of the applet codebase
(in this case, the HTML directory) determined
by the package name.
If the applet is at
http://www.thedomain.com/applet/
Then the Viewer class should be in
http://www.thedomain.com/applet/com/adobe/acrobat/Viewer.class
OTOH, the best thing to do is put it in a jar
archive and include the archive name in
the 'archive' attribute of the applet element.
Lets say the viewer and all the other
classes required, were in a jar called
viewer.jar, which itself was in the same
directory as the applet and web page.
You might change the call like this..
<html>
<body>
<applet code="SampleReader.class"
archive="applet.jar, viewer.jar"
width=900 height=140></applet>
...
This also assumes your two applet classes are
put in archive 'applet.jar' - then the browser
should find all classes.
...What
I need to be able to do is make sure
the applet can be downloaded and run
by any user
Expect a snow storm in Hades, before that
happens. (Or to put that a less obscure way).
You can never *gaurantee* that an end user
will have the correct Java, or any Java,
or that some browser plug-in, browser
manufacturer reaction to a patent challenge,
or any of a dozen other things, causes an
applet to 'not load and run properly'.
As a developer you can take a variety of
measures to help inform an end user that
something has gone wrong, but even in that,
there are no gaurantees.
HTH
Andrew T.