15711 - Can't call java.lang.Class methods from JS

Status: VERIFIED FIXED

(Rhino Graveyard :: Core, defect, P3)

Description

[Patrick C. Beard]

If I do the following:

js> o = new java.lang.Object();
js> c = o.getClass();
js> c.getName();

It doesn't work, because classes only reflect the static methods of a
class, but not the instance methods of java.lang.Class. Should we fix
this? If, so how? Here's one way to fix this:  each java.lang.Class is
wrapped in Rhino as a NativeJavaClass instance. We could  create a
NativeJavaObject wrapper for the class object that reflects the instance
methods, and make that the prototype of the NativeJavaClass. Then we
would have any public static methods defined on the class shadow methods
that come from java.lang.Class, but those could be called by accessing
the prototype.
0

Comment 1

[Scott Furman]

If this is how Rhino LiveConnect works (or doesn't work, as the case may
be), then Rhino acts differently from the way LiveConnect works in
Mozilla and all previous releases of LiveConnect.  LiveConnect has always
treated 'java.lang.Object' and '(new java.lang.Object()).getClass()' as two
distinctly different types of objects.  The former object has as properties all
the static members of the java.lang.Object class and the latter is a JS
wrapper around an instance of java.lang.Class.

Comment 2

[Patrick C. Beard]

I've verified that we now have the correct "LiveConnect" behavior.

Comment 3

[Simon Paquet [:sipaq]]

Status CLOSED is deprecated as per bug 169885

Comment 4

[Simon Paquet [:sipaq]]

Re-Resolving

Comment 5

[Simon Paquet [:sipaq]]

verifying former CLOSED bugs

Comment 6

[Igor Bukanov]

Trageting as resolved against 1.5R5

Comment 7

[Igor Bukanov]

Untargeting wrong milestone assignment

Comment 8

[Pulsebot]

Pushed by ffxbld-merge:
https://hg.mozilla.org/releases/mozilla-beta/rev/7d385b7f1bdd
[fenix] For https://github.com/mozilla-mobile/fenix/issues/15711: Also add custom engines to fallback list.