Hi, On Thu, 2 May 2002 06:39, Robert wrote: > I am curious about the features of the Excalibur datasource component in > comparison to what is going on in the Commons DBCP project. We are > currently using PoolMan as our pooling mechanism as it seemed highly > recommended on the Struts list, but it is no longer supported by the > author, so we are looking for possible alternatives.
PoolMan is a great product and if you are happy with it then I wouldn't give up on it yet. Geir Magnusson Jr. <[EMAIL PROTECTED]> (another Apache guy) has taken over maintanence and management of PoolMan so it should live on ;) As for comparing PoolMan vs the others (Commons and Excalibur). The basic difference is that the PoolMan does more caching and will safely close all used resources when you "close" the connection. ie If you forgot to close a ResultSet and then closed the connection, neither commons nor excalibur will close the ResultSet for you (at least not last time I looked). Excaliburs one is a little faster than PoolMan but more importantly it is already integrated into Avalon framework. However it may be a better idea for you to wrap PoolMan in an Avalon componant (with same interface as Excaliburs Datasource) if you already rely on features of PoolMan. -- Cheers, Peter Donald -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
