[ http://issues.apache.org/jira/browse/GERONIMO-1004?page=comments#action_12323301 ]
Gianny Damour commented on GERONIMO-1004: ----------------------------------------- I am OK with moving the code to OpenEJB as a short term solution. I think that the long term solution is to pass the TransactionManagerDelegate to the SequenceTablePrimaryKeyGenerator and suspend and resume the transaction from there. This implies some changes to the PKGenBuilder interface. I will work on that tonight. > SequenceTablePrimaryKeyGenerator transaction handling is broken (Tranql) > ------------------------------------------------------------------------ > > Key: GERONIMO-1004 > URL: http://issues.apache.org/jira/browse/GERONIMO-1004 > Project: Geronimo > Type: Bug > Components: transaction manager > Versions: 1.0-M5 > Reporter: David Jencks > Assignee: Gianny Damour > Fix For: 1.0-M5 > Attachments: pkgenerator.diff > > Tranql's SequenceTablePrimaryKeyGenerator thinks it is doing its work in a > new transaction, but it is not. It breaks the current transaction, and fails > if you are using an xa datasource. > The current openejb setup code does not allow for passing a separate ds in > for the pk generator than for cmp. Therefore it appears that essentially > doing a "requires new" call is best. However, the transaction module classes > are not available in tranql since transaction depends on tranql (using a > cache class). I think moving the SequenceTable pk generator to openejb is > the most practical short term solution but I will look for others. -- 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
