Hi, I saw this excellent post by Clinton http://www.nabble.com/Proper-transaction-code-pattern-(was:-Autocommit-not-properly-handled-in-Ibatis)-td8505967.html#a8505967
and after a few hours of playing around + googling, I was wondering if someone can clear up the case of ibatis + BasicDataSource + Spring DAO + DataSourceTransactionManager + autocommit. I think this would benefit others too as this is a common setup. I've managed to turn off autocommit by changing the BasicDataSource.defaultAutoCommit property However I was under the assumption that leaving autocommit off in this scenario, I would still be able to commit using sqlMapClient.begin, commit, endTransaction but this is not the case. Would appreciate if someone can expand on the following: - is the appropriate place to turn auto commit off in BasicDataSource in this scenario? - if auto commit is off in this manner, should sqlMapClient.start, commit, endTransaction work? - if auto commit is off and using Ibator to generated SpringDAO's, my records no longer persist to the DB. If this scenario is supposed to use sqlMapClient.start, commit, endTransaction, can Ibator generate? Thanks -- View this message in context: http://www.nabble.com/Ibatis-%2B-apache-BasicDataSource-%2B-Spring-DAO-%2B-autocommit-tp26018335p26018335.html Sent from the iBATIS - User - Java mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
