Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <9038587.1182790465910.JavaMail.jira@brutus>
Date: Mon, 25 Jun 2007 09:54:25 -0700 (PDT)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Closed: (GERONIMO-906) Component references involved in
 transaction recovery are too complicated
In-Reply-To: <1557430476.1124827928724.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

David Jencks closed GERONIMO-906.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Wish List)
                   2.0-M7

Rev 550546 reversed the component references.  This made the code somewhat simpler.  Unfortunately I let IDEA optimize all the imports in the geronimo-connector module.... I hope this doesn't make the change too hard to review.

> Component references involved in transaction recovery are too complicated
> -------------------------------------------------------------------------
>
>                 Key: GERONIMO-906
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-906
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>    Affects Versions: 1.0-M5
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.0-M7
>
>
> The connection manager gets a reference to the TransactionContextManager, which ought to be enough.  However, the TransactionManagerImpl has a reference collection that the MCFWrapper registers with, the TM then calls the recovery methods.
> We should be able to move the recovery methods to TCM and have the connection manager call them after it has started.  We'll also have to look into what to do with the MDB/inbound recovery.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.