Return-Path: X-Original-To: apmail-db-torque-dev-archive@www.apache.org Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A2AB79E36 for ; Wed, 25 Apr 2012 02:48:33 +0000 (UTC) Received: (qmail 18005 invoked by uid 500); 25 Apr 2012 02:48:33 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 17934 invoked by uid 500); 25 Apr 2012 02:48:33 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 17921 invoked by uid 99); 25 Apr 2012 02:48:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 02:48:32 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 02:48:30 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 1C76840D158 for ; Wed, 25 Apr 2012 02:48:09 +0000 (UTC) Date: Wed, 25 Apr 2012 02:48:09 +0000 (UTC) From: "Thomas Fox (JIRA)" To: torque-dev@db.apache.org Message-ID: <1648660094.1390.1335322089117.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (TORQUE-196) Make transaction handling pluggable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Thomas Fox created TORQUE-196: --------------------------------- Summary: 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-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org