[
https://issues.apache.org/jira/browse/OPENJPA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick resolved OPENJPA-149.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
Added new WASRegistryManagedRuntime which extends RegistryManagedRuntime.
WASRegistryManagedRuntime implements the doNonTransactionalWork method and
takes advantage of the WebSphere proprietary UOW API.
I also committed binary versions of the WebSphere UOW API in order to resolve
compile time dependencies. These binary files are not included in our jars and
are not redistributed. The license agreement for use of these binaries is
included in openjpa-kernel/src/resources/com/ibm/license.txt. This may need to
be moved to a more correct location in the future.
> 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
> Fix For: 1.2.0
>
>
> 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.
