[ https://issues.apache.org/jira/browse/TORQUE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261261#comment-13261261 ]
Thomas Fox commented on TORQUE-196: ----------------------------------- The idea is to leave the pubblic interface of the transaction class as and where it is, but make it a holder which delegates all calls to an implementation class which implements an interface TransactionManager (with the same methods as the Transaction class but non-static). The default implementation class would be TransactionManagerImpl and would be set in the init method of Torque. Other implementation classes can be specified in the runtime using the key torque.transactionManager > Make transaction handling pluggable > ----------------------------------- > > Key: TORQUE-196 > URL: https://issues.apache.org/jira/browse/TORQUE-196 > Project: Torque > Issue Type: Improvement > Components: Runtime > Reporter: Thomas Fox > > Currently, the transaction management cannot be changed by the user on a > general basis (i.e. it is possible to handle transactions totally outside > Torque by passing a database connection into the methods, but there is no > place to plug in an own transaction management into torque).This makes using > external transaction management systems (e.g. Spring's @Transactional > annotation) difficult. > To achieve pluggability, the Transaction class should pass all method calls > to an implementation class which can be exchanged by an entry in the Torque > runtime configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org For additional commands, e-mail: torque-dev-h...@db.apache.org