geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-2349) jta 1.1 support with container manager jpa support in transaction module
Date Sat, 26 Aug 2006 17:58:23 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-2349?page=all ]

David Jencks updated GERONIMO-2349:
-----------------------------------

    Attachment: GERONIMO-2349-2.patch

Updated patch that works with current version of sandbox/jee5-jta11/geronimo-transaction-jta11.
 I think that the cm entitymanager implementation is as complete as I can make it for now
until we have actual deployment.  I'd appreciate review of this patch with particular attention
to the question of whether including this implementation in the base classes is appropriate.
 I think it is reasonable to include, but it would also be possible to push it to a TransactionImpl
subclass if we created the TransactionImpl in a protected method.

N.B.  There's a possible bug in ordering of enlisting extended entity managers into transactions
compared to enlisting connections.  I suspect we will need to do something like the InterposedSynch
with the TransactionManagerMonitors so all the connections get enlisted first and delisted
last.  

> jta 1.1 support with container manager jpa support in transaction module
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-2349
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2349
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>    Affects Versions: 1.2
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 1.2
>
>         Attachments: GERONIMO-2349-1.patch, GERONIMO-2349-2.patch
>
>
> We need a strategy for supporting jta 1.1 and parts of jpa in the transaction module
while still passing the j2ee 1.4 signature tests.  Here's a proposal:
> - put the basis for support into the current transaction module, but don't use any jee5
interfaces
> - add an additional transaction-jta11 module that uses the new interfaces and extends
the appropriate classes in transaction.
> I've started along this path.  I'll put the new module in sandbox and supply a patch
for the changes to the existing transaction module.

-- 
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

        

Mime
View raw message