If a <driver> if configured with no <driver-class>, it will attempt to locate the driver(s) via the service loader which should find all JDBC4-compliant drivers. When you install a non JDBC4-complicant driver as a module and no <driver-class>, the driver will not be installed. That is expected but emitting a warning that no-drivers could be found in the module would be useful to help users troubleshoot the problem.
Jeff Zhang <jizhang> updated the status of jira WFLY-2655 to Resolved
Should be easy to backport https://github.com/wildfly/wildfly/commit/fdb6afe7b93ec6fff0ee599e7309d8b682272b18
https://github.com/doctau/jboss-eap/tree/bz1043339 now includes renumbering which has been done upstream. I'm checking with Stefano that it's fine to change in EAP too.
Hi, I am checking the status of this, is the work still required or can the bug be closed? Tom
I'm fine if we NACK this for 6.4, although useful in some circumstance there's not a big demand for it.
Since this didn't get in to 6.4, and it's an enhancement it's unlikely to be done in a CP, so I'm closing it WONTFIX.