Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <432656976.1126577371865.JavaMail.jira@ajax.apache.org>
Date: Tue, 13 Sep 2005 04:09:31 +0200 (CEST)
From: "David Jencks (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-1004) SequenceTablePrimaryKeyGenerator
 transaction handling is broken (Tranql)
In-Reply-To: <861129945.1126561230518.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/GERONIMO-1004?page=comments#action_12323303 ] 

David Jencks commented on GERONIMO-1004:
----------------------------------------

OK.  I guess that is a better solution, since tranql already knows about the tm.  I think we should just wait for your implementation.  If you run into difficulties we have mine as a backup.

> 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