Hi, It looks like the new WebSphere transaction manager lookup code is missing some functionality available elsewhere.
See OPENJPA-149 (https://issues.apache.org/jira/browse/OPENJPA-149) and OPENJPA-153 (https://issues.apache.org/jira/browse/OPENJPA-153) for details. The key problems are: OPENJPA-149: the WASManagedRuntime class throws exceptions on some methods, preventing OpenJPA from being able to suspend transactions OPENJPA-153: even when specifying a non-JTA data source, the data source returned does not allow commits. It does seem like the behavior of the data source is at least a bit different than the JTA data source, since OpenJPA is able to call setAutoCommit(). These seem like usability issues with WAS. I'm hoping that someone with more WAS knowledge than me can resolve the issues easily. Any takers? -Patrick -- Patrick Linskey BEA Systems, Inc. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
