From: <leg...@at...> - 2003-10-03 02:00:20
|
The following comment has been added to this issue: Author: Daniel Bradby Created: Thu, 2 Oct 2003 9:00 PM Body: I applied the patch and it now works fine in WAS 5. Note the WAS 5 no longer supports the UserTransaction name of "jta/usertransaction" for Applications J2EE 1.3 and above, but is now using the default "java:comp/UserTransaction". Have we got somewhere that we could make this clear to the user? --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-365 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-365 Summary: TransactionManagerLookup for WebSphere 5.0 Type: Patch Status: Assigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 2.0.3 Assignee: Daniel Bradby Reporter: Ralf Taugerbeck Created: Fri, 26 Sep 2003 5:08 AM Updated: Sat, 27 Sep 2003 6:21 AM Environment: WebSphere 5.0 Description: The TransactionManagerLookup issue on WebSphere 5.0 was already resolved in HB-240 but IMO the code should look as shown in the attached Patch. BTW, there is no class "com.ibm.ejcs.jts.jta.JTSXA" in WAS 5.0 --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |