Adrian Bartholomew wrote:
>i already have all that put in but its STILL not reading my media files
>past the 1st declared jar file (yes i put the commas).
The references I looked at for the applet tag and its archive attribute are
either ambiguous about eager vs. lazy jar loading, or they explicitly say
it's eager loading. For example, this says "preloaded", which I take to be
eager:
<http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/applet.html>
What you're after is lazy loading. As I vaguely recall, the Java plugin
doesn't do that, only the JNLP loader does, and only as an option. I don't
remember how to get lazy loading with an applet, but it wouldn't surprise
me if you had to do it yourself with a ClassLoader.
If I'm wrong about this, there should be evidence of lazy loading
accomplished with the applet tag's archive attribute somewhere.
Unfortunately, using keywords like lazy or deferred or on demand yielded no
useful hits. If someone else has a reference, please share it.
The question of multiple jars separated by commas is a different issue
entirely. The examples I found in several references show commas and
spaces, but only SAY commas. So I think maybe try commas and spaces.
You can also specify other jars in the Class-Path attribute of a jar
manifest, and they will be loaded as relative URLs from the codebase. It's
been quite a while since I used that with applets, but I recall that it did
work. Read the JAR reference docs about how to put a Class-Path into a jar
manifest.
In general, I suggest creating a small and simple test case, solely to
experiment with how things actually work. You're trying to test a
deployment model using a fully developed applied codebase, and when it
doesn't deploy the way you expect, the failures aren't handled well. There
should be lots of web resources on deploying applets, but if none of them
tell you what you need to know, the only alternative is to find what you
need by your own research, or pay someone to do the research for you.
Also, you should be looking at the post-PHP'ed HTML that's being sent to
the browser, rather than the pre-PHP'ed "source". It's what arrives at the
browser that counts, because the browser is the context that the applet
runs in. "View Source" is a useful browser feature.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
