You can configure commitRequired=true on the tx manager in the SQL Map config file.
Cheers, Clinton On Tue, 18 Jan 2005 18:09:18 +0100 (CET), Andy Light (JIRA) <ibatis-dev@incubator.apache.org> wrote: > [ > http://issues.apache.org/jira/browse/IBATIS-52?page=comments#action_57726 ] > > Andy Light commented on IBATIS-52: > ---------------------------------- > > 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? > > I'll try to fool TM with fake SqlMap update, but you definitely have to do > something about it ;) > > > > Shared data sources > > ------------------- > > > > Key: IBATIS-52 > > URL: http://issues.apache.org/jira/browse/IBATIS-52 > > Project: iBatis for Java > > Type: Improvement > > Components: DAO > > Versions: 2.0.9 > > Reporter: Andy Light > > > > > If I want to use both JDBC transaction manager and SqlMap transaction > > manager for one database, I have to create two separate contexts for them. > > It means that transaction managers will create two data sources and there > > will be two connection pools. Therefore clients from one context are unable > > to participate in transaction from another context, e.g. connection 1 > > cannot see changes made by connection 2 until connection 2 commits and vice > > versa. I have two different transactions after > > daoManager.startTransaction() called and see no way to have one. > > Is it possible to define a single "super"-data source outside contexts, > > give him an alias and reuse it? > > -- > 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 > >
