Leaving the ticket because this is really general discussion.
<snip.>
ok, I can understand this. Any time frame on compositepool / what is needed to get the code release-ready?
As with all things apache, that depends on available volunteer cycles. I posted a straw man roadmap for both [pool] and [dbcp] earlier this week (http://marc.info/?l=jakarta-commons-dev&m=118237533115289&w=4). Comments are welcome. There are some bugs open against the GenericObjectPool impl that I think we should fix in a pool 1.3.1 or 1.4 that could in theory be worked (and maintained) concurrently with pool 2.0. I am willing to do the grunt RM work if others will step up to contribute and most of all review and test. The compositepool impl is in good shape but needs review and testing. There are also some things that could be added or improved if we up the JDK requirement to 1.5 so we can use the concurrent package. Another reason to patch 1.3 is to address things like POOL-97, POOL-93, POOL-102, POOL-86 for direct users of GenericObjectPool and to provide a drop-in fix for tomcat and others who use pool with dbcp while we work on moving dbcp to use pool 2.0. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
