I downloaded newly released version 37.0.1 and tried it again hoping that the bug is fixed.
Unfortunately, it gives the following error when adding the JDBC driver:
--------
10:13:11,494 INFO [
org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on
http://127.0.0.1:9990/management10:13:11,494 INFO [
org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on
http://127.0.0.1:999010:13:11,495 INFO [
org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly 37.0.1.Final (WildFly Core 29.0.1.Final) started in 1214ms - Started 313 of 535 services (330 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml - Minimum feature stability level: community
10:15:07,525 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 4) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("jdbc-driver" => "mysql")
]) - Stage: (RUNTIME) - failure description: "WFLYJCA0041: Failed to load module for driver [com.mysql]"
----------
I used the module.xml file given above as:
-----------
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.9">
<resources>
<resource-root path="mysql-connector-j-9.4.0.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="jakarta.xml.bind.api"/>
</dependencies>
</module>
-----------
But it still does not work.
Before, I asked my 71 students to manually enter the JDBC entry into the standalone.xml file. However, some of them ended up corrupting the file.
After manually entering the JDBC into standalone.xml, I was unable to create a new datasource. It couldn't find the JDBC driver although the info is in the standalone file.
My 71 students and I desperately need a resolution for this issue.