> > 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.
Is there any "standard" way of doing this? I mean, would it be
enough for Turbine's DB pool to implement some interface(s) to
make it pluggable? A la "J2EE DB Pool API"?
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
