Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <32698822.1186511399097.JavaMail.jira@brutus>
Date: Tue, 7 Aug 2007 11:29:59 -0700 (PDT)
From: "Kevin Sutter (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Closed: (OPENJPA-268) Provide pluggable "out of transaction"
 work requests
In-Reply-To: <19224703.1182951206262.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kevin Sutter closed OPENJPA-268.
--------------------------------


> Provide pluggable "out of transaction" work requests
> ----------------------------------------------------
>
>                 Key: OPENJPA-268
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-268
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: kernel
>    Affects Versions: 1.0.0
>            Reporter: Kevin Sutter
>            Assignee: Michael Dick
>
> From the parent Issue (OPENJPA-61)...
> "I don't think that we want this to necessarily be the default ManagedRuntime implementation, since the TSR does not provide any support for executing work in a separate transaction. This behavior is required for sequence maintenance in some scenarios.
> Maybe we should change our ManagedRuntime interface to get rid of the begin() / commit() etc. APIs, and add a new interface for executing a Runnable in a different transaction. This would allow us to use the TSR ManagedRuntime for general use, and just plug in different ways of performing out-of-transaction work." 
> Since the original OPENJPA-61 Issue resolved the first problem with a missing TSR implementation, I created this new sub-task for the "out of transaction" work requests.

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