YAPoolman - Yet Another PoolMan / News: Recent posts

====================
YAPoolMan-1.1 Release
====================
* Fix the bug of JdbcConnectionWrapper which will not validate correctly, and which is the cause of failover of JdbcPool does not function well
* MQSeries, CICS and Corba pooled object implemented.

====================
YAPoolMan-1.0 Release
====================
This is the first release of YAPoolMan
* Can define if a pool manager is global or within context
* All classes user can specify will loaded using context class loader unless it is global
* Web sample is provided

This release has some minor changes over beta1
* Fix error of Exception handling in Proxy invocation
* Two sample classes
* Format comments for testcases

YAPoolMan(From http://sourceforge.net/projects/yapoolman\) is the complete re-write of PoolMan and have more improvements. It inherits major PoolMan features such as

* A centralized xml configuration file

* JDBC driver and data source

* JMX support

However, this project - YAPoolMan, differs quite a lot on the following aspects:

* I believe statement and resultset caching is not necessary, or, for me, I think it is harmful. Since a cached statement should only be used during one check out/check in cycle, most programmer will reuse their statement object anyway, and if you want same statement cached among different users, most modern RDBMS do it quite well. Resultset caching is just a disaster, I never turn it on. The only times I mistakenly turned it on only wasted my time to scratch my head for the mystery broken update code. Besides, caching the result should be better implemented at application level, which means, developer should cache the data object they are interested, rather than the raw material - the resultset. So in YAPoolMan, only connections are pooled.... read more