db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fox (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TORQUE-196) Make transaction handling pluggable
Date Fri, 27 Apr 2012 02:32:48 GMT

     [ https://issues.apache.org/jira/browse/TORQUE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Fox resolved TORQUE-196.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0
         Assignee: Thomas Fox
    
> 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
>            Assignee: Thomas Fox
>             Fix For: 4.0
>
>
> 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-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message