No documentation or errors around method/accessor privacy

[mobiuscog]

When calling Java methods from Rust, it seems that they need to be public - or there may be confusion if they are not.

With a simple test, having a package-protected default constructor, and calling jvm.invoke(..) the returned instance would be invalid. It only seemed to work when making the constructor public.

This may be intentional, or there may be other nuances, but as there is no documentation around this, it becomes confusing to debug. It may also be a bug.

At the very least, it would be useful if there was some documentation around the requirements and/or how accessors/privacy are handled.

[astonbitecode]

Thanks for the report.

j4rs is not designed to interfere with Classes' access. It calls Java like normal Java code calls APIs of other packages. This keeps things simple, enforces cleaner code design and offers better security and behavior predictability.

You are right, there should be a place where this behavior is described. I will update the documentation.