Added documentation on JavaScript-related issues with pulling the

JNLPAppletLauncher from a different web server than the applet and
containing web page

1 files changed, 37 insertions, 1 deletions

diff --git a/www/index.html b/www/index.html
index e96f133..989cbfc 100644
--- a/www/index.html
+++ b/www/index.html
@@ -154,6 +154,13 @@
 
  <p>
 
+ <b>Note</b> that if you are planning to call into your applet from
+ JavaScript that there are some <a
+ href="#SCRIPTING">scripting-related caveats</a> that you need to be
+ aware of.
+
+ <p>
+
  The <code>jnlpExtension</code> parameters passed to the
  JNLPAppletLauncher must be specified with absolute URLs.
 
@@ -234,7 +241,7 @@
  potentially document the need to try restarting the browser in case
  of instability.
 
- <h2>Scripting Support</h2>
+ <h2><a name="SCRIPTING">Scripting Support</a></h2>
 
  <p>
 
@@ -243,6 +250,35 @@
  JavaScript will return the subordinate applet with which you can
  then interact via JavaScript.
 
+ <p>
+
+ There are currently some scripting-related caveats associated with
+ <a href="#ORGANIZING">pulling jar files from multiple locations</a>
+ for a particular applet. In particular, it appears that the
+ LiveConnect security model on Mac OS X in the Safari browser
+ prohibits JavaScript from one domain from communicating with Java
+ code (such as an applet) downloaded from another domain. This is
+ correct according to older versions of the LiveConnect
+ specification, although some more recent implementations of
+ LiveConnect allow this, restricting the privileges of such calls in
+ other ways.
+
+ <p>
+
+ The workaround for this problem seems to be to host the
+ <code>applet-launcher.jar</code> on your web site if you need to
+ talk to your applet from JavaScript. Your applet's jars will likely
+ also need to be hosted from the same web server. If you talk to
+ extension APIs in your <code>archive</code> tag directly from
+ JavaScript, you may find it necessary to host those jars on your
+ web server as well.
+
+ <p>
+
+ From a practical standpoint, most applet developers using
+ JavaScript with the JNLPAppletLauncher will only need to re-host at
+ most <code>applet-launcher.jar</code> on their web site.
+
  <h2><a name="EXAMPLES">Examples</a></h2>
 
  <p>