Hi, I'm using DbForms with commons-dbcp support (due to the modifications to DbConnection class made by Mr Eric Pugh). With DbForms, commons-dbcp is ok and it works well. But DbForms, by default, generates and uses "non-transactional" connections.
Anyway... I also replaced poolman with commons-dbcp in my projects code, and I noticed that dbcp doesn't manage transactions very well... I have problems with method calls like myConnection.setAutoCommit(true), that generates exceptions in the underlying jdbc driver (win2000, jdk1,3 - 1.4, Postgresql 7.2.x with the latest jdbc driver) I also found the same problem into the commons-dev mailing list. http://www.mail-archive.com/[email protected]/msg06342.html Does anyone have problems with dbcp and jdbc transaction management ? I'm going to test Protomatter's JDBC Connection Pool [http://protomatter.sourceforge.net/] and, if it works well, try to integrate it into DbForms. Luca ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
