Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-2619

Refactor ClassFileUtils to operate better on JDK 11+


    • Icon: Enhancement Enhancement
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 3.1.4.Final
    • Proxies
    • None

      There was a series of issues around class loading on JDK 11+ and those problems persist.
      We need to take a look at how to twist the logic in ClassFileUtils to work on JDK 11 without getting IllegalAccess warnings.

      Note that this concerns only SE and maybe Servlet as all EE integrators should use the new API that delegates class defining on them.

      One way is doing a multirelease JAR where we can keep current approach (cracking open CL with setAccessible() for JDK 8 and changing this file for JDK 11 using modular way of adding classes. I know last time I checked, there was a problem with:

      • default packages - you always needed to add classes into existing package which is not what we currently do when we need to replace packages for proxies
      • another problem was not being able to define classes with different ProtectionDomain, I am not certain how we use this and if it is even an issue in SE.

      Another way could be to define our CL since then we would have full access to those methods. But I think this would likely do more harm then anything else.

      I am open to more suggestions mkouba@redhat.com

            Unassigned Unassigned
            manovotn Matěj Novotný
            1 Vote for this issue
            2 Start watching this issue