The correct connfiguration was the first one, but you have put wrong class name into driver/driver-class. You have to put there the vendor class implementing java.sqlDriver interface that for JTS is net.sourceforge.jtds.jdbc.Driver

regarding the error of last post, the problem is that you haven't specified driver tag into datasource that is mandatory. driver-name is the attribute variable mapping into the model this tag. I agree with you that in this case the error is misleading. I'll have a look if it is possible to have an exception easier to read and understand.

Thank you for your insights. I tried changing the JDBC driver as you recommended, but discovered that it still does not work. I changed the driver info on the JTDS to be XA-datasource and that still failed.

I did discover that the JTDS module has not been able to create the .index file which leads me to believe it may be a problem with the JAR itself, but I have not identified exaclty what it is.

Happy you find a workaround. More properly you are using another driver which work out of the box with your setting since it is jdbc 4 compliant. Let me explain better why JTDS is not working with your config.

We have 2 possible case for jdbc driver:

jdbc 4 compliant drivers. In a nutshell they have (according to jdbc 4 spec) a file specifying the name of vendor class implementing Driver. There is a metadata info about that in jar's META-INF. This is the kind of driver you can use with hot deploy because we are able to get autotically the Driver class name. In the same way you can deploy it as module without specifying the driver/driver-class element in standalone xml.

jdbc 3 or earlier version. You have to deploy it as module and you have to specify driver-class in standalone.xml driver element. The correct config in your case should be: