-
Bug
-
Resolution: Done
-
Major
-
1.8.5.Final
-
None
When trying to start up WFLY with JDK 11 (using standalone.sh, I am getting this error:
org.jboss.modules.ModuleNotFoundException: java.se at org.jboss.modules.Module.addPaths(Module.java:1266) at org.jboss.modules.Module.link(Module.java:1622) at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) at org.jboss.modules.Main.main(Main.java:437)
Output of java -version:
openjdk version "11-ea" 2018-09-25 OpenJDK Runtime Environment 18.9 (build 11-ea+21) OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
- blocks
-
JBWS-4129 Can't deploy webservice on JDK11
-
- Resolved
-
-
ENTESB-10072 Can't install fuse on EAP 7.2 with Java 11
-
- Closed
-
-
WELD-2516 Weld TS execution with JDK 11
-
- Resolved
-
-
WFCORE-4211 Missing docs: Embedded container does not work without the JVM being launched with java.se module on Java 11
-
- Resolved
-
- is blocked by
-
WINDUP-2149 Run RHAMT on JDK 11
-
- Closed
-
- relates to
-
WFCORE-3962 Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
-
- Resolved
-
I took a stab at this in https://github.com/Ladicek/jboss-modules/commits/emulated-java-se-module and would appreciate any comments. Especially if this approach has any chance of being accepted
The one question I wasn't able to answer on my own is: should the org.jboss.modules.emulated.java.se module have its own distinct name, or should it be called java.se. I opted into the former option, as it seems less invasive. The latter option would be more transparent, but might have unintended consequences that I'm not aware of.
With the current name, I was able to confirm with Thorntail that adding --add-modules java.se is no longer necessary, but only after I changed the definition of the javax.api module from WildFly (as that refers directly to the java.se name).