This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have been working since 9:00 this morning (it is now 1:45 pm) trying to get a Connection Pool working inside of Tomcat using JSP and Servlets, but to no avail. I then realized that Tomcat is not an application server, and by default, Connection Pooling not supported. They have some Libs that aid in using Connection Pooling in Tomcat, but there seems to be a lot of configging. So I downloaded Resin, copied my web app over, made 1 entry in the resin.conf file, and shazzam!! Connection Pooling Success!! No more Tomcat for Gregg!!
Frank introduced me to Resin and Tomcat was uninstalled from my machine shortly thereafter. The things that make Tomcat easy to use are just as easy in Resin and the areas where Tomcat is a pain are generally easy in Resin as well. I think that the only thing I have discovered that I like about Tomcat better is a faster start up. Since you don't have to restart the server to redeploy the app, it is not that important.
I actually wondered about restarting Resin when I made changes. I was doing it just out of habit. But you don't have to? Another thing I like about Resin is their documentation is so much easier to read and understand. Right now I am getting ready to see how easy it is to deploy along side Apache and get them synced up. Tomcat was a pain to do this, so now it is testing time...