. McClanahan wrote:
On Thu, 11 Apr 2002, Soefara Redzuan wrote:
Date: Thu, 11 Apr 2002 10:46:14 +0800
From: Soefara Redzuan [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Tomcat 4.x and Database Connection Pooling
Tomcat: As far as I'm
On Thu, 11 Apr 2002, Soefara Redzuan wrote:
Date: Thu, 11 Apr 2002 10:46:14 +0800
From: Soefara Redzuan [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Tomcat 4.x and Database Connection Pooling
Tomcat: As far as I'm concerned, JNDI
, Soefara Redzuan wrote:
Date: Thu, 11 Apr 2002 10:46:14 +0800
From: Soefara Redzuan [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Tomcat 4.x and Database Connection Pooling
Tomcat: As far as I'm concerned, JNDI support is a now and forever
In the javabean.
import javax.naming.NamingException;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingEnumeration;
import javax.naming.directory.InitialDirContext;
class mybean() {
java.sql.Connection conn
Hi,
I'm developing a web application using the Struts framework, running on
Tomcat 4.0.3, from which I need to access a MySQL database. I've read
various mailing lists etc looking for the best way to achieve this, but
not had much luck.
Struts provides a basic Connection Pool, but user
if performance is a critical requirement, than I would suggest writing a
custom bean specific to the jdbc driver you intend to use. If Jakarta
common provides all the features you need, than go with it.
If your application needs to support multiple databases and jdbc
drivers, be warned that not
Performance isn't so important as future-proofing - I don't want to have
to re-write the db interface when struts drops it's connection pool
provision, for example.
I believe that mm.mysql does support pooling, although I take your point
that others may not. I can't see us moving away from
Hi Ric,
Struts provides a basic Connection Pool, but user comments suggest that
this is not suitable for large-scale, high-traffic applications, and
also that it will soon be removed from Struts in favour of a
container-managed connection pool
So what will Tomcat Users do? Will Tomcat get a
Not sure - probably a little out of my depth here, but poolman
(www.codestudio.com), which used to do connection pooling stuff is no
longer available, and it's author claims that:
If you are looking for connection and object pooling
mechanisms, they can now be found in
On Wed, 10 Apr 2002, rainer jünger wrote:
Date: Wed, 10 Apr 2002 17:18:34 +0200
From: rainer jünger [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: Tomcat 4.x and Database Connection Pooling
Hi Ric,
Struts provides
: Tomcat 4.x and Database Connection Pooling
Not sure - probably a little out of my depth here, but poolman
(www.codestudio.com), which used to do connection pooling stuff is no
longer available, and it's author claims that:
If you are looking for connection and object pooling
Hi Craig,
So what will Tomcat Users do? Will Tomcat get a container manages
connection
pool?
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/jndi-resources-howto.html
What is the reason for removing it form Struts?
That was a hypothetical example of a possible future situation that
Hi Jim,
If you are looking for connection pooling which will work with any
database
check out DbConnectionBroker at http://www.javaexchange.com/
DbConnectionBroker is only providing as the developer calls it a 2 Tier
model. So there is not actually a Connection Pool that manages the
On Wed, 10 Apr 2002, rainer jünger wrote:
Date: Wed, 10 Apr 2002 18:42:39 +0200
From: rainer jünger [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: Tomcat 4.x and Database Connection Pooling
Hi Craig,
So what
Hi Craig,
Sorry somehow I don't understand your answer.
Struts is ***NOT*** going to remove its own connection pool :-).
Thanks thats an answer even I can understand ; ).
However, the internal implementation is changing in Struts 1.1 to use the
commons-dbcp implementation
Tomcat: As far as I'm concerned, JNDI support is a now and forever more
feature of Tomcat 4 and later. It's the standard access mechanism for J2EE
app servers as well.
This is what I love to hear. With so many changes (servlets to JSP to
Struts) over the last few years, future-proofing is
Performance isn't so important as future-proofing - I don't want to have
to re-write the db interface when struts drops it's connection pool
provision, for example.
I believe that mm.mysql does support pooling, although I take your point
that others may not. I can't see us moving
Struts provides a basic Connection Pool, but user comments suggest that
this is not suitable for large-scale, high-traffic applications, and
also that it will soon be removed from Struts in favour of a
container-managed connection pool
So what will Tomcat Users do? Will Tomcat get
18 matches
Mail list logo
