Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.1.1
-
None
Description
I had the same need in an older version and I had to do a terrible hack which I would not like to do with a newer version.
The main idea is that I would like to be able to monitor borrow and return events (among other things) and for that I need to provide my own GenericObjectPool implementation.
It would be a small change to add a createObjectPool method and use it in createConnectionPool. Default implementation would be to
if (abandonedConfig != null && (abandonedConfig.getRemoveAbandonedOnBorrow() || abandonedConfig.getRemoveAbandonedOnMaintenance())) { gop = new GenericObjectPool<>(factory, config, abandonedConfig); } else { gop = new GenericObjectPool<>(factory, config); }
Subclasses would have the flexibility to provide their own pool implementation.