on 2/15/01 3:24 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]>
wrote:
> However, I would not recommend it ... the turbine-pool.jar file drags along
> ~40 classes of Turbine infrastructure that aren't useful unless you are
> running inside Turbine.
What *exactly* is the problem with that?
> Of course, no third part connection pool at all is needed if your app server
> provides one for you. And, as long as the server obeys the conventions
> described in the servlet and J2EE specs w.r.t. <resource-ref> entries and the
> corresponding JNDI context provided by the server (which is in the near-term
> plans for Tomcat 4 as well, with plug-in of any conforming data source), the
> app doesn't care. It's portable, instead of locked in to a particular
> implementation.
Point being...where is Tomcat going to get its implementation of a
connection pool from? Are you going to re-implement Struts pool again? :-)
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/> && <http://java.apache.org/turbine/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
