SqlMap transaction not commited after JDBC-based update
-------------------------------------------------------
Key: IBATIS-54
URL: http://issues.apache.org/jira/browse/IBATIS-54
Project: iBatis for Java
Type: Bug
Versions: 2.0.9
Reporter: Andy Light
[Moved from IBATIS-52 issue comments]
I used JDBC under SqlMap transaction manager, but encountered another problem:
1. I call daoManager.startTransaction()
2. I take a connection in JDBC DAO from JDBCDaoTemplate and execute an UPDATE
(or INSERT) statement on it.
3. I call daoManager.commitTransaction();
Note that the only action was on JDBC DAO.
No SqlMap DAO participated in this case.
What I have: no commit on connection.
Reason: "session.isCommitRequired()" in TransactionManager.commit(Session);
It seems, that SqlMap transaction manager hasn't intercepted my UPDATE on
connection and therefore thinks that no commit is required as no action was
done.
Am I right?
BTW, if fake UPDATE (no rows really updated) is executed using SqlMap after
JDBC UPDATE, commit works OK.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
