You need to configure JBoss to use its own connection pool.
See Chapter 8 of the getting started guide.
Or read the WIKI
J2EE has special pooling requirements that the xadatasource or jdbc driver
will not understand.
Thanks. I am sorry but after I read chap.8 of the get started guide again and wiki page, I still have got the point. I think I know how to config the -ds.xml. What I was asking is:
Jboss does not care if the driver that is provided in datasource can do pooling or XA, JBoss just simply wrap this driver up and use JBoss's own connection pooling mechanism and XA? Therefore I should only need provide a basic jdbc driver without any pooling capability for the datasource?
If this is true, what if I provide a XA-compliant driver? Does it have any difference to JBoss?
You will still want an XA driver for the database to correctly participate in two phase commit protocol. JBoss won't be able to do that if the driver does not support it.