-
1. Re: org.jboss.modules.ModuleNotFoundException: java.se
simkam Nov 27, 2018 8:59 AM (in response to mayerw01)Hi,
I think it is [WFLY-10937] Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se - JBoss Issue Tracker which will be fixed in WildFly 15.
-
2. Re: org.jboss.modules.ModuleNotFoundException: java.se
mayerw01 Nov 27, 2018 10:45 AM (in response to simkam)This link refers to the same issue. But I've now made the change the appclient.sh
eval \"$JAVA\" $JAVA_OPTS \
--add-modules java.se \
-cp "$CLASSPATH" \
...
This seems to work
-
3. Re: org.jboss.modules.ModuleNotFoundException: java.se
jenskreidler Apr 12, 2019 7:45 AM (in response to mayerw01)Thanks Wolfgang for your workaround, nevertheless I had the following issues:
- adding jvm arguments in arquillian.xml will not work when using a remote-container, and as far as I know the "wildfly-arquillian-container-embedded" is entitled embedded but will bootstrap a fully-fledged server - not any embedded wildfly libraries (so behaves like expected in my case as "remote container")
- using wildfly-arquillian-container-embedded in verion 2.2.0.Final still needs the jvm argument "--add-modules=java.se"
- In my case I added the configuraion in the maven-failsafe configuration:
<configuration> <argLine>--add-modules=java.se</argLine> [...] </configuration>