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 written several JSF applications which implement database access now. However, I still feel that there must be a better way to manage database connections. Currently, my technique is to create a single serializable bean which every other bean within my application will extend. I put all of my "shared" methods and such within this bean including my database connection method. This seems to work fine, but it is causing multiple connections from a single user to occur each time the application is utilized.
Is there a better method of controlling database access within my JSF applications?
Yes, I agree that a connection pool is the best way to go. I am using an OracleConnectionPool Cache Manager to connect to my database. Still, even with the connection pool I am seeing multiple connections. I thought that the connection pool was supposed to alleviate this problem?
Thanks in advance for any suggestions...
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com