Bob Anderson wrote:
> I'm not familiar with the details of your DB connection pool, but I just thought I'd
>offer this consideration: In our custom framework, we decided that our db connections
>should NOT extend
> java.sql.connection, because we didn't want anyone to close a connection.
In our pool our conections implement java.sql.Connection, and they wrap
the real connection, giving access to all methods (doing some check to
see if the connection is available or not), except the close(), which
does nothing. :-) Only the pool can access the close() method of the
real connection.
This makes things easier when testing our classes outside of the web
server. I just open a connection in a main() method and call the exact
same class. (We do not use Turbine because I think when we began this
Turbine was still not available, or at least I had never heard about,
and now it would be too much work to migrate things).
On a side note, our system uses a very simple templating engine I wrote,
that is pretty bare-bones, but fast, and has everything we need here
(keyword substitution, including of other templates, loops and ifs).
Could be something to contribute also. :-)
--
[]'s
Marcelo Vanzin
Touch Tecnologia
[EMAIL PROTECTED]
"We're an underground revolution working overtime"
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
