WebSphere 6.1 JNDI DS Provider - PostgreSQL JDBC provider implementation classname needs to be stipulated

When setting up a JNDI DS provider under WebSphere 6.1, an implementation classname is required. For PostgreSQL, there are currently two providers that can be used according to http://jdbc.postgresql.org/documentation/84/ds-ds.html:

Applications: DataSource

PostgreSQL™ includes two implementations of DataSource , as shown in Table 11.2, "DataSource Implementations". One that does pooling and the other that does not. The pooling implementation does not actually close connections when the client calls the close method, but instead returns the connections to a pool of available connections for other clients to use. This avoids any overhead of repeatedly opening and closing connections, and allows a large number of clients to share a small number of database connections.

The pooling data-source implementation provided here is not the most feature-rich in the world. Among other things, connections are never closed until the pool itself is closed; there is no way to shrink the pool. As well, connections requested for users other than the default configured user are not pooled. Its error handling sometimes cannot remove a broken connection from the pool. In general it is not recommended to use the PostgreSQL™ provided connection pool. Check your application server or check out the excellent jakarta commons DBCP project.

Table 11.2. DataSource Implementations

Pooling Implementation Class
No org.postgresql.ds.PGSimpleDataSource
Yes org.postgresql.ds.PGPoolingDataSource

Both implementations use the same configuration scheme. JDBC requires that a DataSource be configured via JavaBean properties, shown in Table 11.3, "DataSource Configuration Properties", so there are get and set methods for each of these properties.

Can the required provider be discovered and explictly documented as the one a customer using WebSphere 6.1 connecting to a PostgreSQL DB must use.