JDK11 holds GlassFish back - monitoring issue to collect all such things

[dmatej]

As we are still discussing which Java version should be used as a base for future JEE, I decided to create this issue to collect all issues we have collided with on the path to modern GlassFish. When we find some solution, these problems will split to a standalone issues and solutions.

Default methods vs. Proxies vs. InvocationHandler

• see https://bugs.openjdk.org/browse/JDK-8253870 - there is no way how to execute a default method of an interface on generated proxy from another module in JDK11. In JDK16+ there is a InvocationHandler.invokeDefault for this purpose and I have tested it would work.
• It would be useful ie as a replacement for all those DuckTypes.
• Reproducer - add this method to the SimpleConnector class (unit tests of hk2-config)

  default String hello() {
      return "hello";
  }
  

  Then add () -> assertEquals("hello", connector.hello()) to ConfigTest.testDefaultValuesFromConfig()

Microprofile support

• Helidon requests JDK17+
• For now we have implemented way to filter out microprofile from dependencies at runtime if the server runs on older JDK.
• See also https://github.com/eclipse-ee4j/glassfish/issues/24125

[dmatej]

JDK for GF8.0.0 will be JDK 21, just FYI.

[github-actions[bot]]

This issue has been marked as inactive and old and will be closed in 7 days if there is no further activity. If you want the issue to remain open please add a comment

[github-actions[bot]]

This issue has been marked as inactive and old and will be closed in 7 days if there is no further activity. If you want the issue to remain open please add a comment