JACE correctly "fudges" the method name when
generating the proxy, e.g. if the Java method name
is 'delete' then on generation it creates a proxy method
name of 'delete_'. However, when calling the method at
runtime, it doesn't "unfudge" it and it tried to call a Java
method called 'delete_' instead of one called 'delete'.