openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-149) non-jta-data-source must be specified in WebSphere environments
Date Tue, 31 Jul 2007 19:17:53 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516781
] 

Kevin Sutter commented on OPENJPA-149:
--------------------------------------

Clarifying a couple of my earlier comments...

The use of non-jta-data-sources in WebSphere will allow the use of DB2 Sequences.  This support
does not require the ability to suspend the current transaction.  But, it would still be nice
to have the ability to access database sequences without requiring the use of non-jta-data-sources.
 This transaction suspension can be done via WebSphere's UOWSynchronizationRegistery API.
 We should use this JIRA Issue to track this additional "feature".  In the mean time, WebSphere
users should use the spec-compliant non-jta-data-source element.

Through discussions with Patrick, he has indicated a desire to make this support more general
so that it could apply to other environments more easily.  He has opened OPENJPA-159 for this
purpose.  Thus, these two Issues (OPENJPA-159 and OPENJPA-149) are very much related.

Just wanted to clarify my earlier comments and what the differences are between 149 and 155.

Kevin

> non-jta-data-source must be specified in WebSphere environments
> ---------------------------------------------------------------
>
>                 Key: OPENJPA-149
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-149
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: kernel
>    Affects Versions: 0.9.6
>         Environment: WebSphere
>            Reporter: Patrick Linskey
>            Assignee: Kevin Sutter
>            Priority: Blocker
>             Fix For: 0.9.8
>
>
> The suspend(), resume(), begin(), and commit() methods in org.apache.openjpa.ee.WASManagedRuntime$WASTransaction
all throw exceptions. This prevents the logic in org.apache.openjpa.jdbc.kernel.AbstractJDBCSeq
from executing. See OPENJPA-144 for relevant stack traces. In particular, look at the Only-JTASpecified.txt
trace.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message