On 7/30/01 9:58 AM, "Diethelm Guallar, Gonzalo" <[EMAIL PROTECTED]>
wrote:
> We use Resin for most of our development and some of our deployments.
> A few days ago, we had a discussion about Turbine's services and how
> pluggable they are, and the issue of DB pools came up. Please bear
> with me if this is a basic question...
>
> Is it possible to plug a different implementation of a DB pool into
> Turbine's service, so that the rest of the code does not change, but
> now the servlet is using, say, Resin's DB pool? What requirements
> would a DB pool (such as Resin's) implementation have in order for
> it to be pluggable? Does this make any sense?
It is currently not possible to use another connection pool with
Torque, but it is something that will be addressed shortly because
if Torque is going to be a general persistence layer than the
connection _must_ be pluggable.
I mentioned this exact same thing on the Struts list yesterday
hoping someone would take up the challenge. Torque can be made
to use any connection pool it will just require some work but
Torque has to move in that direction if it's going to be
a general tool usable outside the confines of turbine.
> Thanks,
>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
