openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <>
Subject [jira] Resolved: (OPENJPA-149) non-jta-data-source must be specified in WebSphere environments
Date Fri, 25 Apr 2008 20:31:55 GMT


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

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:
>             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$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

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

View raw message