[
https://issues.redhat.com/browse/ELY-1979?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on ELY-1979:
---------------------------------------
Elytron requires Java 11 to build so as you say looks like it should just be a case of
adding the missing methods and passing then through to a delegate when appropriate. We
don't expect users of these classes to access them using any approach other than the
standard API they expose so as for example SSLEngine doesn't contain those methods on
the older releases if anyone bypasses that it will be expected to fail.
Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl
package
---------------------------------------------------------------------------
Key: ELY-1979
URL:
https://issues.redhat.com/browse/ELY-1979
Project: WildFly Elytron
Issue Type: Bug
Components: SSL
Affects Versions: 1.12.0.Final
Reporter: Brian Stansberry
Assignee: Darran Lofthouse
Priority: Blocker
Fix For: 1.12.1.CR1
JEPS 244, available in JDK 9 or later and in JDK 8 since the 251 release[1] has added new
methods to some of the javax.net.ssl classes that elytron wraps in
org.wildfly.security.ssl. But the elytron classes do not handle those new methods. I
believe the relevant change is at [2] and updates the SSLEngine, SSLParameters and
SSLSocket classes (plus various non-javax classes.)
If Elytron were to require 251 or later to build perhaps this could be a simple matter of
adding new methods to the wrappers and calling the delegate, under the expectation that at
runtime the wrapper methods would not be invoked in a JVM < 251. Or the wrappers could
use reflection and throw a UOE if the methods are not available.
[1]
https://www.oracle.com/technetwork/java/javase/8u251-relnotes-5972664.htm...
[2]
https://hg.openjdk.java.net/jdk8u/jdk8u41/jdk/rev/b26b096d4c89
--
This message was sent by Atlassian Jira
(v7.13.8#713008)