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?
Thanks,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
