Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8142422

Smaller Dynalink API adjustments

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 9
    • 9
    • core-libs
    • 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.

            attila Attila Szegedi
            attila Attila Szegedi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: