Can someone explain the difference between the (oh, let's pick one) mysql-ds.xml file and the mysql-service.xml file in 3.2?
From reading the startup logs, it looks like the -ds.xml approach creates a LocalTxConnectionManager, and the necessary JBossManagedConnectionPool. So, is the -ds.xml descriptor, simply an easy way to deploy a datasource in just a few lines? If so, bravo. It was needed.
So what configuration options can we add to a -ds.xml file? Can I control the min/max pool size, or how to react to an error condition? Some of these values appear to be defaulted when the connection manager is initialized, so where do these settings come from?
yes, it's transformed into a *-service file using xsl, which is then deployed normally.
You can specify everything in a *-ds.service file. I think nearly everything available is shown in the generic-ds.xml example.