Hi, Note: the tomcat JNDI binding support is not specific to connection pooling. You can do a lot more (and most people do a lot less ;)) with JNDI. It's a generic mechanism.
What you probably meant is how does PoolMan compare to commons-dbcp, which is the connection pooling implementation used in tomcat 4.1.x. As for that, I can't help much ;) I only used a really old version of PoolMan a long time ago, and it was fine. I use DBCP now, and it's fine. A possible trump card for me is that development on DBCP is active and ongoing, whereas PoolMan is pretty much done. Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: neal [mailto:[EMAIL PROTECTED]] >Sent: Thursday, August 29, 2002 12:10 AM >To: Tomcat Users List >Subject: Poolmam vs. Tomcat's JNDI (DBCP, Pool) > >Do you guys prefer Tomcat JNDI over PoolMan? > >It is looking like (from the multiple installs and the significant >configuration details) that Poolman is a lot easier to setup and use that >Tomcat's JNDI option. Anyone have an opinion? > >Thanks. >Neal > > >-- >To unsubscribe, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]>
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
