> I did, because the other connection type is not pooled, among > many things. I can revert the changes if it is a bad idea.
It's only bad because it breaks my code :-) The code I'm using is (I think) very common, I'm simply turning autocommit off. Now, I know that in a managed environment I wouldn't do that, but as Tomcat doesn't have a Transaction Manager I can't see any other way to do my own transaction management. Unless anybody shouts loudly (and can show me how to do TXs with JDBC under Tomcat) I'd love to see the change reverted. > From the commons. It will be used in the next Tomcat, as it > is a lot easier to use and configure (in addition to the > maintenace and visibility problems Tyrex has). Excellent - which version of Tomcat is this going to be in (4.1?). Thanks for the response, Kevin Jones Developmentor www.develop.com > -----Original Message----- > From: Remy Maucherat [mailto:[EMAIL PROTECTED]] > Sent: 03 April 2002 16:17 > To: Tomcat Developers List > Subject: Re: Tyrex exception when using tomcat 4.0.4 (b1 and b2) > > > > but if the tyrex guys are retired who's changed this in TC4.0.4? > > > > BTW what is DBCP? > > > Remy > > > -- > To unsubscribe, e-mail: > <mailto:tomcat-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
