[ http://issues.apache.org/jira/browse/IBATIS-52?page=comments#action_57729 ] Andy Light commented on IBATIS-52: ----------------------------------
Just want you to know that fake update helped. Everything seems to work OK now, but I hope you'll fix your library as this workaround is dirty. > 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
