[ http://issues.apache.org/jira/browse/GERONIMO-2349?page=all ]
David Jencks updated GERONIMO-2349:
-----------------------------------
Attachment: GERONIMO-2349-v5.patch
This is getting out of control... I'd like to scale back this issue to the
changes in the transaction module itself and deal with persistence-refs in a
separate issue (GERONIMO-2383).
Please consider this patch together with the sandbox jta11 modules and vote
soon.
> 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,
> GERONIMO-2349-3.patch, GERONIMO-2349-v4-plus-2163-openejb.patch,
> GERONIMO-2349-v4-plus-2163.patch, GERONIMO-2349-v5.patch,
> persistencecontextref.zip
>
>
> 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