Synchronize with website prior to 1.6R2 release.

docs/api.html

@@ -73,33 +73,33 @@ <h4>
 The Host Object API</h4>
 These APIs provide support for adding objects specific to a particular
 embedding of JavaScript in a host environment. Note that if you just want
-to script existing Java classes, you should just use <a href="http://devedge.netscape.com/library/manuals/2000/javascript/1.5/guide/lc.html">LiveConnect</a>. See also <a href="http://www.mozilla.org/js/liveconnect/">LiveConnect 3.0 specs</a>.
+to script existing Java classes, you should just use <a href="http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Guide:LiveConnect_Overview">LiveConnect</a>. See also <a href="http://www.mozilla.org/js/liveconnect/">LiveConnect 3.0 specs</a>.
 It is also helpful to understand some of the implementation of the <a href="runtime.html">runtime</a>.
 <ul>
 <li>
-<a href="org/mozilla/javascript/Scriptable.html">Scriptable</a> - All JavaScript
+<a href="apidocs/org/mozilla/javascript/Scriptable.html">Scriptable</a> - All JavaScript
 objects must implement this interface. Provides methods to access properties
 and attributes of those properties, as well as other services required
 of JavaScript objects.</li>
 
 <li>
-<a href="org/mozilla/javascript/Function.html">Function</a> - All JavaScript
+<a href="apidocs/org/mozilla/javascript/Function.html">Function</a> - All JavaScript
 functions must implement this interface. Extends Scriptable, adding methods
 to support invocation.</li>
 
 <li>
-<a href="org/mozilla/javascript/ScriptableObject.html">ScriptableObject</a>
+<a href="apidocs/org/mozilla/javascript/ScriptableObject.html">ScriptableObject</a>
 - A default implementation of Scriptable that may be extended. Implements
 property and attribute storage and lookup and other default JavaScript
 object behavior.</li>
 
 <li>
-<a href="org/mozilla/javascript/FunctionObject.html">FunctionObject</a>
+<a href="apidocs/org/mozilla/javascript/FunctionObject.html">FunctionObject</a>
 - An implementation of Function that allows Java methods and constructors
 to be used as JavaScript function objects.</li>
 
 <li>
-<a href="org/mozilla/javascript/ImporterTopLevel.html">ImporterTopLevel</a>
+<a href="apidocs/org/mozilla/javascript/ImporterTopLevel.html">ImporterTopLevel</a>
 - Allows embeddings to use the JavaImporter constructor.</li>
 </ul>
 
@@ -108,22 +108,22 @@ <h4>
 These exceptions are thrown by JavaScript.
 <ul>
 <li>
-<a href="org/mozilla/javascript/RhinoException.html">RhinoException</a>
+<a href="apidocs/org/mozilla/javascript/RhinoException.html">RhinoException</a>
 - Common root for all exception explicitly thrown by Rhino engine.</li>
 
-<a href="org/mozilla/javascript/JavaScriptException.html">JavaScriptException</a>
+<a href="apidocs/org/mozilla/javascript/JavaScriptException.html">JavaScriptException</a>
 - Thrown from within JavaScript by the JavaScript 'throw' statement. It wrapps the JavaScript value from 'throw' statement.</li>
 
 <li>
-<a href="org/mozilla/javascript/WrappedException.html">EcmaError</a>
+<a href="apidocs/org/mozilla/javascript/WrappedException.html">EcmaError</a>
 - Thrown by Rhino runtime when particular runtime operation a scripts tries to execute is not allowed. The exception is thrown, for example, when a script attempts to check properties of <tt>undefined</tt>or <tt>null</tt> or refer to a name that can not be found in the current scope chain.</li>
 
 <li>
-<a href="org/mozilla/javascript/WrappedException.html">WrappedException</a>
+<a href="apidocs/org/mozilla/javascript/WrappedException.html">WrappedException</a>
 - Thrown by LiveConnect implementation from JavaScript when called Java method exits with an exception. It wraps the original Java exception.</li>
 
 <li>
-<a href="org/mozilla/javascript/EvaluatorException.html">EvaluatorException</a>
+<a href="apidocs/org/mozilla/javascript/EvaluatorException.html">EvaluatorException</a>
 - An exception thrown when an error is detected during the compilation or execution of
 a script. The default error reporter will throw EvaluatorExceptions when
 an error is encountered.</li>

docs/embedding-engine.html

@@ -52,7 +52,7 @@
 language in detail but explains how these scripting engines can be used
 as host to expose business objects in the middle-tier and how the user
 of these applications can extend it if needed using JavaScript.</font></font>
-<p><font face="Arial"><font size=-1>The scripting engine Rhino (<a href="http://www.mozilla.org/js)">www.mozilla.org/rhino)</a>,
+<p><font face="Arial"><font size=-1>The scripting engine Rhino (<a href="./)">www.mozilla.org/rhino)</a>,
 a javascript engine purely written in Java is one that I am going to use
 for the testing the above.</font></font>
 <p><font face="Arial"><font size=-1>Let us set some simple goals,</font></font>
@@ -161,7 +161,7 @@
 <br><font face="Arial"><font size=-1>Object any=null;</font></font>
 <br><font face="Arial"><font size=-1>try{</font></font>
 <br><i><font face="Arial"><font size=-1>//Enter the Context</font></font></i>
-<br><font face="Arial"><font size=-1><i>// Refer </i><u><font color="#0000FF">http://www.mozilla.org/js/rhino/tutorial.html</font></u></font></font>
+<br><font face="Arial"><font size=-1><i>// Refer </i><u><font color="#0000FF">http://www.mozilla.org/rhino/tutorial.html</font></u></font></font>
 <br><font face="Arial"><font size=-1>Context context = Context.enter();</font></font>
 <br><i><font face="Arial"><font size=-1>// Get the execution scope</font></font></i>
 <br><font face="Arial"><font size=-1>Scriptable scope = context.initStandardObjects();</font></font>
@@ -183,7 +183,7 @@
 scope);</font></font>
 <br><font face="Arial"><font size=-1>scope.put("create",scope,create);</font></font>
 <br><i><font face="Arial"><font size=-1>//Evaluate (or execute js)</font></font></i>
-<br><font face="Arial"><font size=-1><i>//Refer </i><u><font color="#0000FF">http://www.mozilla.org/js/rhino/tutorial.html</font></u></font></font>
+<br><font face="Arial"><font size=-1><i>//Refer </i><u><font color="#0000FF">http://www.mozilla.org/rhino/tutorial.html</font></u></font></font>
 <br><font face="Arial"><font size=-1>any = context.evaluateString(scope,
 jsbuff, "", 1, null);</font></font>
 <br><i><font face="Arial"><font size=-1>//Exit the Context</font></font></i>
@@ -266,8 +266,8 @@
 <br>&nbsp;
 <br>&nbsp;
 <p><font face="Arial"><font size=-1>For more explanations on the code execution,
-please refer embedding tutorial <a href="http://www.mozilla.org/js/rhino/tutorial.html">http://www.mozilla.org/js/rhino/tutorial.html</a>
-and for all documentation and examples on Rhino visit <a href="http://www.mozilla.org/rhino/doc.html">http://www.mozilla.org/rhino/doc.html</a>.</font></font>
+please refer embedding tutorial <a href="http://www.mozilla.org/rhino/tutorial.html">http://www.mozilla.org/rhino/tutorial.html</a>
+and for all documentation and examples on Rhino visit <a href="doc.html">http://www.mozilla.org/rhino/doc.html</a>.</font></font>
 <br>&nbsp;
 <br>&nbsp;
 <br>&nbsp;

docs/examples.html

@@ -68,7 +68,7 @@ <h4>
 <br>&nbsp;
 <h2>
 Implementing Host Objects</h2>
-First check out the <a href="http://www.mozilla.org/rhino/tutorial.html">tutorial</a>
+First check out the <a href="tutorial.html">tutorial</a>
 if you haven't already.
 <h4>
 The Foo class - Extending ScriptableObject</h4>

docs/javaone.html

@@ -33,7 +33,7 @@ <h3>
 Java classes visible to scripts</h3>
 One attendee raised the point that many embeddings may not want scripts
 to be able to access all Java classes. This is an excellent point, and
-I've implemented an addition to the <a href="../js/rhino/org/mozilla/javascript/SecuritySupport.html">SecuritySupport</a>
+I've implemented an addition to the <a href="apidocs/org/mozilla/javascript/SecuritySupport.html">SecuritySupport</a>
 class that allows embedders to choose which classes are exposed to scripts.
 <h3>
 Easier "importing" of Java classes</h3>
@@ -42,7 +42,7 @@ <h3>
 could be improved. I've implemented a set of changes that make importing
 easier, but I'm not convinced that adding them is the right thing to do
 due to some drawbacks.
-<p>To see what I've done, take a look at the javadoc for the <a href="../js/rhino/org/mozilla/javascript/ImporterTopLevel.html">ImporterTopLevel</a>
+<p>To see what I've done, take a look at the javadoc for the <a href="apidocs/org/mozilla/javascript/ImporterTopLevel.html">ImporterTopLevel</a>
 class. You'll see that it's now possible to make function calls to "import"
 Java classes so that they can be referred to without qualification. I didn't
 use the word "import" because that's a keyword in JavaScript.

docs/limits.html

@@ -81,6 +81,6 @@ <h3>
 <p>The Microsoft SDK 3.1 for Java also exhibits this problem.
 <p>
 <hr WIDTH="100%">
-<br><a href="rhino.html">back to top</a>
+<br><a href="#">back to top</a>
 </body>
 </html>

docs/rhino15R1.html

@@ -80,7 +80,7 @@ <h3>
 can be used to create Java classes from JavaScript. Options exist to allow
 creation of Java classes that implement arbitrary interfaces and extend
 arbitrary base classes, allowing JavaScript scripts to implement important
-protocols like applets and servlets. See <a href="http://www.mozilla.org/rhino/jsc.html">http://www.mozilla.org/rhino/jsc.html</a>.
+protocols like applets and servlets. See <a href="jsc.html">http://www.mozilla.org/rhino/jsc.html</a>.
 <br>&nbsp;
 <h3>
 LiveConnect 3</h3>
@@ -102,7 +102,7 @@ <h3>
 New semantics for <tt>ScriptableObject.defineClass</tt></h3>
 The old rules for defining JavaScript objects using a Java class were getting
 baroque. Those rules are still supported, but a cleaner definition is now
-supported. See the <a href="http://www.mozilla.org/js/rhino/org/mozilla/javascript/ScriptableObject.html#defineClass(org.mozilla.javascript.Scriptable, java.lang.Class)">javadoc</a>
+supported. See the <a href="apidocs/org/mozilla/javascript/ScriptableObject.html#defineClass(org.mozilla.javascript.Scriptable, java.lang.Class)">javadoc</a>
 for details.
 <br>&nbsp;
 <h3>
@@ -119,15 +119,15 @@ <h3>
 Java classes visible to scripts</h3>
 An attendee at JavaOne raised the point that many embeddings may not want
 scripts to be able to access all Java classes. This is an excellent point,
-and I've implemented an addition to the <a href="../js/rhino/org/mozilla/javascript/SecuritySupport.html">SecuritySupport</a>
+and I've implemented an addition to the <a href="apidocs/org/mozilla/javascript/SecuritySupport.html">SecuritySupport</a>
 interface that allows embedders to choose which classes are exposed to
 scripts.
 <br>&nbsp;
 <h3>
 SecuritySupport and JavaAdapter</h3>
 Andrew Wason pointed a problem with the new JavaAdapter feature (which
 allows JavaScript objects to implement arbitrary Java interfaces by generating
-class files). It didn't support the <a href="../js/rhino/org/mozilla/javascript/SecuritySupport.html">SecuritySupport</a>
+class files). It didn't support the <a href="apidocs/org/mozilla/javascript/SecuritySupport.html">SecuritySupport</a>
 interface, which allows Rhino to delegate the creation of classes from
 byte arrays to a routine provided by the embedding. This ability is important
 from a security standpoint because class creation is considered a privileged
@@ -140,14 +140,14 @@ <h3>
 Context.exit()</h3>
 Context.exit() has been changed from an instance method to a static method.
 This makes it match the Context.enter() method, which is also static. See
-the <a href="http://www.mozilla.org/js/rhino/org/mozilla/javascript/Context.html#exit()">javadoc</a>
+the <a href="apidocs/org/mozilla/javascript/Context.html#exit()">javadoc</a>
 for more information on its operation.
 <br>&nbsp;
 <h3>
 Context.enter(Context)</h3>
 A new overloaded form of Context.enter has been added. Without the addition
 of this method it was not possible to attach an existing context to a thread.
-See the <a href="http://www.mozilla.org/js/rhino/org/mozilla/javascript/Context.html#enter(org.mozilla.javascript.Context)">javadoc</a>
+See the <a href="apidocs/org/mozilla/javascript/Context.html#enter(org.mozilla.javascript.Context)">javadoc</a>
 for more information on its operation.
 <br>&nbsp;
 <h3>