Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-5408

Remove GraalVM reachability metadata specific to org.mongodb:mongodb-crypt from :driver-core

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 5.2.0
    • Affects Version/s: None
    • Component/s: GraalVM
    • None
    • Fully Compatible
    • Java Drivers
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      When org.mongodb:mongodb-crypt with the changes made in JAVA-5407 is released, and MongoDB Java driver depends on that new version, we should remove the reachability metadata that was added in JAVA-5407 to org.mongodb:mongodb-crypt from :driver-core (for example, the whole driver-core/src/main/resources/META-INF/native-image/jni-config.json was copied to org.mongodb:mongodb-crypt and should be removed from :driver-core).

      Important: despite the following metadata entries having been added to bindings/java/mongocrypt/src/main/resources/META-INF/native-image/reflect-config.json in org.mongodb:mongodb-crypt, they must remain in :driver-core, because they are also used by :driver-core

      {
        "name":"sun.security.provider.NativePRNG",
        "methods":[{"name":"<init>","parameterTypes":[] }, {"name":"<init>","parameterTypes":["java.security.SecureRandomParameters"] }]
      }
      
      {
        "name":"org.slf4j.Logger"
      }
      

            Assignee:
            valentin.kovalenko@mongodb.com Valentin Kavalenka
            Reporter:
            valentin.kovalenko@mongodb.com Valentin Kavalenka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: