As a proof-of-concept, can we support "one-way" Java object use, in which construction and use of bound types is supported, but no Java-to-managed object references.

This would mean:

• Subclassing is (probably) out
  • though Java-to-managed method invocations should still be possible (static methods?)?
• Managed code could refer to Java instances, e.g. List<Java.Lang.String> works
• Java code can't refer to managed code, e.g. if you could subclass, that subclass couldn't contain any fields which reference any reference types. (Which is why subclassing would be out.)

Ideally, such a limited construct could be done via a JniRuntime.JniValueManager subclass.