Hi All, I am developing a web-based application using Cocoon 1.8, and am using Turbine for SQL connection pooling - Turbine is a neat application. In our own support classes, we manipulate data based on querying connections - all standard stuff, indeed. However, just in case we need to deploy into another environment, I've provided an abstraction layer to serve connections by pool name, which happens to call Turbine. My question is this: Is there any particular reason that the DBConnection class does not implement the java.sql.Connection interface? I notice that the implementation code is present, but commented - if I enable this code, does it break anything in particular, and secondly, can this be enabled in the core distribution. Supporting the java.sql.Connection interface directly means that my abstraction layer has no external dependancy on Turbine, and allows it to provide access to pooled sql connections, regardless of underlying implementation. I can submit a diff file if required, but the changes are minimal in either case, as the code is already there. Many thanks Adrian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
