Morten Norby Larsen wrote:
>This seems to indicate that a possible workaround could be to keep the jar
>at the same directory level as the web page (at least as seen from the
>browser). I just checked the server logs, and this is indeed what happens:
>the browser sends a request for the jar at the page's directory level.
Good detective work.
Another possible workaround, which I have not tried, might be this:
<OBJECT type="application/x-java-applet"
classid="java:AppletTest"
archive="test/AppletTest.jar"
width="150" height="150">
Java applet with a red background.
</OBJECT>
It avoids the codebase attribute, which is what seems to be broken. The
reasoning is that both the codebase and archive attributes are URI's, and
codebase should be prepended to an archive, classid, or data attribute's
relative URI. So just prepend it manually since it isn't being prepended
by Safari/WebKit.
I can't test this right now, but I should be able to later tonight or tomorrow.
-- 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
