In case could not be somelike connected with this issue?
To be clear this is just about deploying the latest version of the MySQL driver into the AS.
Basically, pop the driver into the deployments folder and it didn't work.
It looks like an OSGi issue so not really sure if its JCA but its certainly not TM.
Override using the <driver-class> element in <driver>
Tom Jenkinson <firstname.lastname@example.org> updated the status of jira JBTM-2121 to Closed
we should at least consider using first driver in services/java.sql.Driver as default
Current behavior confuses a lot of users.
First class is already used when driver is in module and data-source class isn't specified while adding driver. See. https://bugzilla.redhat.com/show_bug.cgi?id=1107120
Giving a second thought about this.
Doing this way (comment #11) would cause problems in case of upgrading jdbc drivers (this bz is an example).
If we use one driver by default (arbitrary policy about picking one of the listed in the jar file), we are making this problem not visible. This could cause a problem (possible use of the wrong driver, not supported, not tested, etc...). I think is better to leave the behaviour as it is. It seems consistent to me.