#105 IClass: new safe filtered version

已關閉
ranides2 年之前創建 · 2 條評論

We can write new IClass implementation which implements all possible checks inside all methods (interfaces, parents, methods, fields etc).

We will test it under JDK 11 to see warnings.

This new implementation probably will be just alternative version of RClass - all other classes are more or less dependent on internal IClass field and there is a chance that "safe-logic" implemented in parent would be enough.

If not, another attempt would be adding final boolean safe flag into every implementation.

Anyway, to create this safe version we will call non-static IClass#safe method which will produce new, safe version.

This safe class would be enough to solve problems with BeanModel.

We can write new IClass implementation which implements all possible checks inside all methods (_interfaces_, _parents_, _methods_, _fields_ etc). We will test it under JDK 11 to see warnings. This new implementation probably will be just alternative version of RClass - all other classes are more or less dependent on internal IClass field and there is a chance that "safe-logic" implemented in parent would be enough. If not, another attempt would be adding `final boolean safe` flag into every implementation. Anyway, to create this safe version we will call non-static `IClass#safe` method which will produce new, safe version. This safe class would be enough to solve problems with `BeanModel`.
ranides 評論 2 年之前'
所有者

see #102

see #102
ranides 評論 2 年之前'
所有者

This task is good place for resolving general problem with net.ranides.assira.reflection.util.ReflectUtils#access

In JDK 9+ we should use AccessibleObject.canAccess() and forget about AccessibleObject.isAccessible()

This task is good place for resolving general problem with `net.ranides.assira.reflection.util.ReflectUtils#access` In JDK 9+ we should use AccessibleObject.canAccess() and forget about AccessibleObject.isAccessible()
ranides1 年之前 關閉
登入 才能加入這對話。
未選擇里程碑
未指派成員
1 參與者
正在加載...
取消
保存
尚未有任何內容