If the underlying Jdbc driver provides connection pooling, should the application still use Jdbc connection pooling of BES?
For the transactional use case, If one were to use Jdbc-connection-pooling of the underlying driver (and not configuring BES pool at all), the transaction glue code (to integrate appserver transactions with database transactions) will need to be written by the user. This integration is reasonably involved, and becomes trickier with distributed (XA) transactions.