anonymous wrote : | 15.5.3.1 Auto Commit | When a Connection is in an auto-commit mode, an Interaction, associated with the Connection, automatically commits after it has been executed. The auto-commit mode must be turned off if multiple interactions have to be grouped in a single transaction and committed or rolled back as a unit. | CCI does not provide explicit set/getAutoCommit methods in the Connection interface. This simplifies the application programming model for the transaction management. | A resource adapter must manage the auto-commit mode as follows: | A transactional resource adapter either at the XATransaction or | LocalTransaction level must set the auto-commit mode of Connection | instances participating in a transaction to off within the transaction. This | requirement holds for true both container-managed and bean-managed | transaction demarcation. | A transactional resource adapter must set the auto-commit mode of Connection instances to on when used outside a transaction. | These requirements are independent of whether a transaction is managed as a local or XA transaction. A transactional resource adapter should implement this requirement in an implementation-specific manner. | A non-transactional resource adapter at the NoTransaction level, is not required to support the auto-commit mode for Connection. |
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926012#3926012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3926012 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
