[
https://issues.apache.org/jira/browse/OPENJPA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sutter updated OPENJPA-149:
---------------------------------
Fix Version/s: 0.9.7
Priority: Blocker
Affects Version/s: 0.9.6
I am assigning this Issue to version 0.9.7, although it really doesn't require
a change in the OpenJPA code. This Issue is dependent on a change in the
WebSphere code that should be in the Beta release for the EJB3/JPA Feature
Pack. I will also assign this Issue to myself for tracking purposes.
> 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
> Assigned To: Kevin Sutter
> Priority: Blocker
> Fix For: 0.9.7
>
>
> 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.
