openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <>
Subject [jira] Commented: (OPENJPA-268) Provide pluggable "out of transaction" work requests
Date Wed, 27 Jun 2007 18:26:26 GMT


Patrick Linskey commented on OPENJPA-268:

> Are there cases where we need "transactional" semantics but 
> "not the transaction currently bound" to the Broker?

If a non-transactional data source is not provided, then we need this for sequence table updates

Reducing the number of required data sources is nice from an ease-of-use standpoint.

> Provide pluggable "out of transaction" work requests
> ----------------------------------------------------
>                 Key: OPENJPA-268
>                 URL:
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: kernel
>    Affects Versions: 1.0.0
>            Reporter: Kevin Sutter
> 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.

View raw message