[
https://issues.jboss.org/browse/WFCORE-1431?page=com.atlassian.jira.plugi...
]
Tomaz Cerar updated WFCORE-1431:
--------------------------------
Description:
With JDK9 jigsaw builds remoting and most tests related to it fail.
Problem is in org.xnio.sasl.SaslUtil.getFactories()
Which doesn't work correctly on Jigsaw as it prevents us form loading classes from
java base image as they are not exported.
as workaround we have
{noformat}
-XaddExports:java.security.sasl/com.sun.security.sasl.digest=ALL-UNNAMED,java.security.sasl/com.sun.security.sasl=ALL-UNNAMED
{noformat}
but we should have proper solution.
was:
With JDK9 jigsaw builds remoting and most tests related to it fail.
Problem is in org.xnio.sasl.SaslUtil.getFactories()
Which doesn't work correctly on Jigsaw as it prevents us form loading classes from
java base image as they are not exported.
as workaround we have
-XaddExports:java.security.sasl/com.sun.security.sasl.digest=ALL-UNNAMED,java.security.sasl/com.sun.security.sasl=ALL-UNNAMED
but we should have proper solution.
Look into loading Sasl providers on jigsaw
------------------------------------------
Key: WFCORE-1431
URL:
https://issues.jboss.org/browse/WFCORE-1431
Project: WildFly Core
Issue Type: Sub-task
Components: Remoting
Affects Versions: 2.1.0.CR1
Environment: JDK9 Jigsaw
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
With JDK9 jigsaw builds remoting and most tests related to it fail.
Problem is in org.xnio.sasl.SaslUtil.getFactories()
Which doesn't work correctly on Jigsaw as it prevents us form loading classes from
java base image as they are not exported.
as workaround we have
{noformat}
-XaddExports:java.security.sasl/com.sun.security.sasl.digest=ALL-UNNAMED,java.security.sasl/com.sun.security.sasl=ALL-UNNAMED
{noformat}
but we should have proper solution.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)