Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.6.0
-
None
-
None
Description
For both reflective and generic UD(A)F, I've noticed cases where an incorrectly written Java class will cause UDF creation or execution to fail, but with poor diagnostics (e.g. NPE or non-obvious Java reflective exception), requiring the user to guess what the problem is by comparison with a working class.
Specific examples to follow; I think I have seen the following cases:
- incorrect accessibility on a class or method (e.g. private instead of public)
- missing no-arg constructor
- incorrect method return type