Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 7 Aug 2003 10:56 AM
This was already fixed in CVS. IBM changed things behind our backs. The latest implementation supports both variations.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-240
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-240
Summary: The net.sf.hibernate.transaction.WebSphereTransactionManagerLookup invokes a non-existant method on a JTSXA object
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Versions:
2.0 final
Assignee:
Reporter: Tomasz Jankowski
Created: Thu, 7 Aug 2003 9:35 AM
Updated: Thu, 7 Aug 2003 10:56 AM
Environment: Experienced on a Win2k machine running WebSphere Enterprise Studio/WebSphere 5.0, the code involved does NOT seem to be platform dependent but IS appServer dependent
Description:
Specifying a JNDI DataSource in hibernate.cfg.cml when running on WebSphere 5.0 will produce errors related to the transaction.manager_lookup_class. The class to specify for this property is net.sf.hibernate.transaction.WebSphereTransactionManagerLookup according to the Hibernate documentation.
The bug is reproduced when the return statement is reached in the getTransactionManager(Properties) method of the lookup class. That statement tries to dynamically invoke a static method getTransactionManager() on the com.ibm.ejs.jts.jta.JTSXA class - the problem is that there's no such method. The fix is to call the correct method: instance().
Original code:
.
.
return (TransactionManager) clazz
.getMethod("getTransactionManager", null)
.invoke(null, null);
.
.
Suggested correction (tested by overloading the original):
.
.
return (TransactionManager)clazz.getDeclaredMethod("instance", null).invoke(null,null);
.
.
Thanks!
---------------------------------------------------------------------
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
|
