Message:
The following issue has been closed.
Resolver: Daniel Bradby
Date: Mon, 13 Oct 2003 4:11 AM
Fixed
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-383
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-383
Summary: websphere 5 transaction manager lookup
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1
Versions:
2.1 beta 4
Assignee: Daniel Bradby
Reporter: Edina Pimp
Created: Tue, 7 Oct 2003 11:54 AM
Updated: Mon, 13 Oct 2003 4:11 AM
Environment: WebSphere Platform 5.0 [BASE 5.0.2]; Win2k; WSAD; JDK1.3.1
Description:
Newest version of the WebSphereTransactionManagerLookup fails under WebSphere 5. Class com.ibm.ejs.jts.jta.JTSXA - which is the default class - remains available in the classpath so it's found and Hibernate assumes a WAS4 environment.
When 'getTransactionManager' is invoked on the WAS5 version of JTSXA, a NoSuchMethod exception is thrown, caught, and rethrown as a HibernateException. The correct method is instance().
This worked in 2.1b3 because the exception handling just happened to line up the right way.
Maybe it's reasonable to break out different WebSphere4TransactionManagerLookup and WebSphere5TransactionManagerLookup classes, ugly as it sounds.
---------------------------------------------------------------------
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
|
