Sorry for interrupting.
As for the standalone setup, the driver name is the file name of the JAR dropped into /standalone/deployments according to http://docs.jboss.org/ironjacamar/userguide/1.0/en-US/html/deployment.html#deployingds_descriptor (Table 5.13, driver description).
However, I'm still facing two problems. For whatever reason, at server startup the datasource is never configured on the first try:
04:00:55,224 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) Bound data source [java:jboss/datasources/ExampleDS]
04:00:55,238 INFO [org.jboss.as.deployment] (MSC service thread 1-2) Started FileSystemDeploymentService for directory C:\dev\jboss7\standalone\deployments
04:00:55,244 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found bbstats.war in deployment directory. To trigger deployment create a file called bbstats.war.dodeploy
04:00:55,456 INFO [org.jboss.as.controller] (Controller Boot Thread) Service status report
New missing/unsatisfied dependencies:
service jboss.jdbc-driver.mysql-connector-java-5_1_13-bin_jar (missing)
04:00:55,496 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "mysql-connector-java-5.1.13-bin.jar"
04:00:55,716 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
04:00:55,727 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) Bound data source [java:jboss/datasources/BBStatsDS]
04:00:55,728 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Final "Lightning" started in 3213ms - Started 112 of 169 services (57 services are passive or on-demand)
04:00:55,783 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployed "mysql-connector-java-5.1.13-bin.jar"
04:00:55,783 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) Service status report
Newly corrected services:
service jboss.jdbc-driver.mysql-connector-java-5_1_13-bin_jar (now available)
Then, as you can see from the "
Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)" my driver is also flagged to be non-JDBC, but it clearly is JDBC 4-compliant.