You are correct, there is no way supported by jboss to supply a DataSource implementation backed by pooling in a non-jboss vm. Is there some reason we should be supporting this? If you really want it, you could implement a default ConnectionManager that did some pooling for the Local jdbc wrapper, and write a few lines to create a ManagedConnectionFactory and ConnectionFactory (DataSource, here) using the default ConnectionManager. You can recycle the InternalManagedConnectionPool code for the pooling. I did this for the firebird jca-jdbc driver (in the FBWrappingDataSource).