configuration. With a single container running multiple apps this is
a bit of an issue.
Edgar
-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]
Sent: Monday, November 24, 2003 11:03 PM
To: Struts Users Mailing List
Subject: RE: Server manged vs. struts managed db
Edgar P Dollin wrote:
There is another issue regarding connection pooling in struts vs connection
pooling in the container. In struts the war file contains all the
information the app needs to run. With container pooling (at least with
tomcat and resin) you have to coordinate the container
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 25, 2003 6:17 AM
To: [EMAIL PROTECTED]
Subject: Re: Server manged vs. struts managed db pools
Edgar P Dollin wrote:
There is another issue regarding connection pooling in struts vs
connection pooling in the container. In struts
Quoting Edgar P Dollin [EMAIL PROTECTED]:
I like struts managed db pools, however, the struts developers aren't too
happy about the quality and the dependency on the commons-pooling library
and are attempting to phase it out.
The existing connection pool in struts-legacy.jar (and the one in
Tomcat has exceptionally clear documentation in this area:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
Mike
--- Craig R. McClanahan [EMAIL PROTECTED] wrote:
Quoting Edgar P Dollin [EMAIL PROTECTED]:
I like struts managed db pools, however, the
I like struts managed db pools, however, the struts developers aren't too
happy about the quality and the dependency on the commons-pooling library
and are attempting to phase it out.
Edgar
-Original Message-
From: Nathan Maves [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18,
6 matches
Mail list logo
