-
Enhancement
-
Resolution: Fixed
-
P4
-
9
-
b93
-
generic
-
generic
Following the CCC review of Dynalink API, I will adopt the following suggestions:
- make CompositeOperation and NamedOperation final
- DynamicLinkerFactory.DEFAULT_UNSTABLE_RELINK_THRESHOLD should not be part of the API
- BeansLinker static discovery method (getReadableInstancePropertyNames and friends) should return Set instead of Collection
- CompositeGuardingDynamicLinker and CompositeTypeBasedGuardingDynamicLinker should not be Serializable.
Additionally, I made TypeUtilities final (it has a private constructor anyway); and added documentation to private StaticClass.clazz field and readResolve() method as their documentation is used in the "Serialized Form" JavaDoc page.
Finally, as a non-API change, AbstractJavaLinker.getConstructorMethod is now abstract and a default implementation returning null added to BeanLinker.
- make CompositeOperation and NamedOperation final
- DynamicLinkerFactory.DEFAULT_UNSTABLE_RELINK_THRESHOLD should not be part of the API
- BeansLinker static discovery method (getReadableInstancePropertyNames and friends) should return Set instead of Collection
- CompositeGuardingDynamicLinker and CompositeTypeBasedGuardingDynamicLinker should not be Serializable.
Additionally, I made TypeUtilities final (it has a private constructor anyway); and added documentation to private StaticClass.clazz field and readResolve() method as their documentation is used in the "Serialized Form" JavaDoc page.
Finally, as a non-API change, AbstractJavaLinker.getConstructorMethod is now abstract and a default implementation returning null added to BeanLinker.