Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <17087049.1165517961673.JavaMail.jira@brutus>
Date: Thu, 7 Dec 2006 10:59:21 -0800 (PST)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Closed: (GERONIMO-1574) Spring integration with Geronimo
 Transaction Manager
In-Reply-To: <1788632669.1138874503357.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-1574?page=all ]

David Jencks closed GERONIMO-1574.
----------------------------------

    Resolution: Won't Fix

After the tx refactoring and global jndi, you should be able to access the geronimo tx manager in spring using the normal spring components.

> Spring integration with Geronimo Transaction Manager
> ----------------------------------------------------
>
>                 Key: GERONIMO-1574
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-1574
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>    Affects Versions: 1.2
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: Wish List
>
>
> For a reasonable spring integration, we need to expose some of our components wrapped in spring interfaces.  The most obvious is the transaction manager.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira