Hi, since I will have to implement a database access, I would like to know what the problems are with PoolMan. And I would be happy to see that code too. Thanks in advance Wolfgang
"Kipnis, Adam" schrieb: > I wouldn't recommend Poolman since I have found it to be pretty problematic. > As for the Singleton vs Servlet approach, I think that's really up to > personal preference. If you put your connection pool logic inside a servlet > and have that servlet load on startup, you're not really that much different > than a standard singleton. Since there are usually more uses for an > application level service other than a connection pool (ie, a global level > internal data caching system), I wrote a services manager as a servlet that > loads all the application level services, including connection pools, on > start-up based on configuration files. If you like, I can send you a copy of > the servlet and associated connection pool. > > -Adam Kipnis > [EMAIL PROTECTED] > > -----Original Message----- > From: Damien VIEL [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 23, 2002 12:20 AM > To: Struts Users Mailing List > Subject: Singleton vs ServletContext > > Hi !! > > My question is about the best way to implement a JDBC ConnectionPool for > Struts. > I've heard that the one that is already in Struts is not a good choice. > I've also read many mails about PoolMan. > In Servlets & JSP book from Marty Hall, he speaks also about Singleton. > > What's the easiest way ? > Has anybody a simple sample ? > > Thanks All. > > Best > > Dams > > -- > 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]>
