Issue1743

This is a regression in 2.5.2 compared to 2.5.1.  In 2.5.1 the attached script produces no output as it should.  In 2.5.2 it fails with java.lang.NegativeArraySizeException.

In a real code I also see 'some_function(): expected 1 args; got 0' when executing 'some_function ('bla')' --- this also worked fine in 2.5.1.

Please disregard 'test.py' --- it is a wrong file.  See this short Java code instead.

Ping...

Interesting usage of Jython's internals

Well, how do I tell apart internals from not? PyNone is in the same package, for instance.

PyReflectedFunction seems to be a good way to make Java methods available to scripts detached from their classes. What I do is collect a number of "very common" methods from my application and make them visible to scripts without importing anything, much like builtins.

Is there a thing to fix here, or just to be clearer what is meant to be public?

Ideally I would of course prefer that original semantics is restored. It was a simple way to make static functions (i.e. something not attached to a "bean") to Jython scripts.

In our application Jython is used for lots of simple scripts (5-30 lines). I prefer to make certain common functions available to them without requiring an explicit imports, i.e. similar to builtins.

Did you try to use Py.newJavaFunc instead of PyReflectedFunction?

How would I even use it? It expects a method in my class that accepts PyObject[] and String[]... Presumably, those are arguments and their names. However, what I'm doing with old PyReflectedFunction (yes, because of this bug I never upgraded to newer Jython) is wrapping arbitrary Java methods with arbitrary argument types. Additionally, PyReflectedFunction can resolve overrides with different number of arguments for me.

(I don't want to argue about this being an issue that needs a fix. Just wanted to suggest a workaround until a fix is available.)
You're right, Py.newJavaFunc requires your function to have a special signature. Regarding the notation in your file test.java, what about the following workaround:

python.exec ("test = System.gc");
python.exec ("test ()");

Did you try that?

No, I didn't try that, but it does look like it'd give the result I need.