www.javaexchange.com had product called DBConnectionBroker. Can't seem to get to their site today, though.
However, I dropped using it after I found (and subsequently fell madly in love with) Turbine. p.s. IMOHO no one really needs a bloated, buggy (admin console in particular) product like WS. And that's coming from an IBM BP ;-) ssshhhh, don't tell anyone I said that though. Scott -----Original Message----- From: Jon Stevens [mailto:[EMAIL PROTECTED]] Sent: Friday, December 07, 2001 2:50 PM To: turbine-dev Subject: Re: Torque connection pooling versus DBCP code in Commons on 12/7/01 11:27 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > It's not a big deal, I've just been looking at the code so that I can better > understand it. We use WebSphere application server to host our application > and are currently relying on its' connection pooling. We really don't need an > expensive product like WebSphere and I've been investigating alternatives to > their connection pooling. No one really needs an expensive product like websphere. Torque's connection pooling is really much more than just a connection pool. It allows us to achieve transparent multiple database support. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
