I am using Oracle 9i and I have made several posts and it does not work. I cannot rollback operations. If I debug inside the daoManager then the code is suppose to roll back for all the contexts in the list. In my case I have defined all the daos inside one context tag. So all the transactions for all the daos should rollback, but it does not happen.
Has anyone used DaoManager to rollback successfully with Oracle 9i. I can write down the details of my design and code again if anyone is interested to help.
I have used all possible configuration in the xml files. No luck. I am too late to give up iBATIS in my project now.
On 6/27/06, jaybytez <[EMAIL PROTECTED]> wrote:
What do these fields do in relation to allowing CMT to handle transactions in
iBatis?
The documentation is not totally clear, and from posts that I have read, I
am not sure if there is conflicting information. Does
commitRequired="false" mean the container handles the transaction without
iBatis interaction, or does commitRequired="true" with DefaultAutoCommit and
SetAutoCommitAllowed mean the container handles the transactions without
iBatis.
Here are my two configs and I cannot tell what the difference is regarding
transactions:
This is my original configuration:
<transactionManager type="EXTERNAL" commitRequired="false">
<dataSource type="JNDI">
<property name="DataSource" value="${fooPool.JNDIName}" />
</dataSource>
</transactionManager>
This appears to be the suggested configuration:
<transactionManager type="EXTERNAL" commitRequired="true">
<property name="DefaultAutoCommit" value="false"/>
<property name="SetAutoCommitAllowed" value="false"/>
<dataSource type="JNDI">
<property name="DataSource" value="${fooPool.JNDIName }" />
</dataSource>
</transactionManager>
Thanks,
jay blanton
--
View this message in context: http://www.nabble.com/commitRequired-%2C-DefaultAutoCommit-%2C-SetAutoCommitAllowed--tf1856695.html#a5070352
Sent from the iBATIS - User - Java forum at Nabble.com.
