The jdbc-driver resource's 'driver-name' attribute is a deprecated bit of cruft that must have the same value as the galleon 'jdbc-driver' param (which becomes part of the resource address).

The h2-driver feature-group is setting it which results in a deprecation WARN message when provisioning.

The datasources subsystem doesn't persist the attribute, so it doesn't show up in the config leading to the WARN during a normal boot. Which is probably why we didn't notice this.

For context: https://wildfly.zulipchat.com/#narrow/channel/196266-wildfly-user/topic/drive-name.20deprecation.20warning/with/528368774