[armedbear-devel] new jcall / jar:file: path functions
alessiostalla at gmail.com
Fri Jan 8 20:11:47 UTC 2010
On Thu, Jan 7, 2010 at 6:48 PM, Alan Ruttenberg
<alanruttenberg at gmail.com> wrote:
> On Thu, Jan 7, 2010 at 11:37 AM, Alessio Stalla <alessiostalla at gmail.com> wrote:
>> On Thu, Jan 7, 2010 at 4:32 PM, Alessio Stalla <alessiostalla at gmail.com> wrote:
>>> On Thu, Jan 7, 2010 at 6:39 AM, Alan Ruttenberg
>>> <alanruttenberg at gmail.com> wrote:
>> At this point, we can either
>> 1. ignore the problem,
>> 2. always call setAccessible(true) before calling a method,
>> 3. try to find the overridden method as up as possible in the class
>> hierarchy before calling it, hoping to get at some point to a public
>> 2. and 3. would make all method calls through jcall less efficient;
>> however, we could enable one of those techniques only when some
>> additional parameter is passed to jcall (e.g. the try-harder that was
>> proposed some time ago for jfield).
> I believe that the code that jss uses a method cache and therefore
> only needs to do the setAccessible call once. Have you looked at what
> jsint.Invoke does or considered simply adopting it for ABCL?
We designed the following solution:
every Java object (instance of JavaObject) carries a reference to its
"intended class", which must be a supertype of the object's class.
The intended class is used to access the object's methods via
reflection; only if a method is not found in the intended class the
more specific object class is used, and only if it's public.
How is the intended class determined? There are two possibilities:
- automatically, by looking at the method return type (for objects
returned by a method call), field type (for objects read from a
field), or class of the object (when it is constructed explicitly with
- manually, through a new operator - (jcoerce obj class)
The automatic way covers the common case of methods returning an
instance of a class or interface implemented via a non-public inner
class, which was the source of the bug.
For more complex cases - for example when an object is an instance
like the above but implements several different interfaces, and must
be accessed specifically through one of them, which might not be the
one that has been chosen automatically - jcoerce comes to help.
This patch is now applied on trunk (rev. 12345) and you are encouraged
to try it and comment on it.
I haven't benchmarked it, but I don't expect a performance
degradation, just a slightly increased memory usage due to the extra
reference to the intended class stored in every JavaObject.
More information about the armedbear-devel