Announcement Announcement Module
Collapse
No announcement yet.
code change for Ibatis internal transaction support Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • code change for Ibatis internal transaction support

    I looked around and did not see how i can submit my change to the project.
    Here is my diff, of the SqlMapClientFactoryBean which allows us to use the Ibatis built in transaction manager and not be forced into the EXTERNAL one.
    I can submit the actual file if you prefer

    > import com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTran sactionConfig;
    > import com.ibatis.sqlmap.engine.transaction.BaseTransacti onConfig;
    63a66,67
    > private boolean externalTransactionManager = true;;
    >
    101a106,109
    > public void setUseExternalTransactionManager(boolean bUseExternalTransactionManager) {
    > this.externalTransactionManager = bUseExternalTransactionManager;
    > }
    >
    120c128,135
    < ExternalTransactionConfig transactionConfig = new ExternalTransactionConfig();
    ---
    > BaseTransactionConfig transactionConfig = null;
    > if (!externalTransactionManager) {
    > transactionConfig = new JdbcTransactionConfig();
    > }
    > else {
    > transactionConfig = new ExternalTransactionConfig();
    > }

  • #2
    You can still post your changes to jira.
    I wonder how powerfull / flexible / transparent is iBatis internal transaction management compared to Spring one?

    Comment


    • #3
      The reason i want this change in, is for cases such as mine, where i do not need the full transaction management Spring provides and i cannot get the current configuration to work with DBCP.
      Do i need to open an issue to put in my code change?

      Thanks,
      David

      Comment

      Working...
      X