[
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: (was: 1.0.0)
It doesn't look like this Issue will be doable before the 1.0.0 cutoff. Since
the spec-compliant means is to use the non-jta-data-source element, WebSphere
has a solution that works. So, this is not a "stop ship" requirement for the
1.0.0 release.
> 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: Michael Dick
> Priority: Blocker
>
> 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.
