[Webkit-unassigned] [Bug 15109] Liveconnect: no window.java object available in the DOM

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=15109


Alexey Proskuryakov <ap at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX
                 CC|                            |ap at webkit.org




--- Comment #7 from Alexey Proskuryakov <ap at webkit.org>  2010-02-25 22:18:12 PST ---
Per
<http://java.sun.com/javase/6/webnotes/6u10/plugin2/liveconnect/index.html>,
the global window.java and window.Packages properties are now deprecated, and
for a good reason:

----------------------------
The Mozilla family of browsers has historically provided support for access to
the Java language from JavaScript even on web pages that don't contain Java
applets. In this browser family, there are global java, netscape and Packages
keywords available to JavaScript code which allow calling static methods,
accessing static fields, and creating new instances of Java classes in similar
fashion to the per-applet Packages keyword above.

The semantics of these keywords becomes problematic when more than one applet
is available on the web page. If you want to access one particular applet's
user-defined classes (for example, in a com.mycompany package), how would the
global Packages keyword know which applet to refer to? The new Java Plug-In
also supports attaching more than one Java virtual machine instance to the web
browser for executing applets. The semantics of these global keywords becomes
even more complicated in this situation.

For this reason, the global java, netscape and Packages JavaScript keywords are
deprecated. They continue to function in the Firefox browser, but it is
strongly recommended to transition existing code using them to use the new
per-applet Packages keyword. It is not possible to access user-defined classes
using these global keywords; attempts to do so will yield undefined results.
----------------------------

We will probably need to support per-applet Packages property at some point,
but I think that the global one is a clear WONTFIX.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.