> or as you say we could use a TIBCO adapter which talks to Oracle database,
well, the term 'adapter' used, was a generic term - for lack of anything
else. this 'adapter' is a simple java class - nothing bulky (assuming TIBCO
adapter is bulky and provides a hunk of features that i don't know of) :-)
> and handles all the connection pooling for us.
that's exactly what this proposed class shall do.
> There are many ways of doing this, but arent we making things more complex
> by making use of adapter, rather using a class or finally block.
i honestly don't know if adding one class makes things complex. here is my
take away on this approach:
+ layer of abstraction to solve a bigger problem.
+enables one to forget the low-level details of connection pooling
+one doesn't need to replicate the code throughout the source base for
handling connections in try catch finally blocks.
> Putting code in finally block is not code redundancy but this is to check
> that the connection is not open, if open then close it and let the gc do
the
> rest.
i agree. i don't say putting code in finally block is redundancy, but if i
have to do that everywhere the persistence layer is called from - then, that
is!
~Manav.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
