and possible more.
I'm currently working towards an overall structure as IronJacamar 1.x in order to keep the concepts similar - e.g. ConnectionManager - Pool - ManagedConnectionPool - ConnectionListener. However, some of the responsibilities will be moved around. F.ex. the pool will be responsible for creating and destroying the ConnectionListener instances, because different pool implementations may use different implementations.
Hence we need to move as much common functionality into abstract classes for maximum reuse.
Initial aim will just be the foundation for the default pool with connection listeners supporting NoTransaction scenarios.
Feel free to share ideas for improvements, and new settings.