Gracefully handle absence of Unsafe.defineAnonymousClass

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P1
    • None
    • Affects Version/s: None
    • Component/s: core-libs
    • None

      With JDK 17, Unsafe.defineAnonymousClass is no more. Nashorn must handle its absence gracefully when --anonymous-classes option is set to "auto" (which is the default). It should still reject starting up if someone explicitly set the option to "true". The behavior when it's set to "false" is unchanged.

            Assignee:
            Attila Szegedi
            Reporter:
            Attila Szegedi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: