[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2457?page=c...
]
Ivo Abeloos commented on HHH-2457:
----------------------------------
I can confirm that the problem still exists:
WAS 6.1.0.11
Oracle 9i
Hibernate 3.2.5GA
First time the session got queried we got the unsupported exception ... Hibernate 3.1.3
works fine.
hibernate properties:
hibernate.connection.datasource=com.company.hibernate.DataSource
hibernate.transaction.manager_lookup_class=org.hibernate.transaction.WebSphereExtendedJTATransactionLookup
hibernate.transaction.factory_class=org.hibernate.transaction.JTATransactionFactory
hibernate.transaction.flush_before_completion=true
hibernate.transaction.auto_close_session=true
hibernate.current_session_context_class=jta
hibernate.cache.provider_class=org.hibernate.cache.EhCacheProvider
UnsupportedOperationException with
WebSphereExtendedJTATransactionLookup
------------------------------------------------------------------------
Key: HHH-2457
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2457
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.2
Reporter: Erik Post
Using the WebSphereExtendedJTATransactionLookup as transaction manager lookup class
results in an UnsupportedOperationException being thrown by
WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter.getStatus(). This method
is called by JTATransactionFactory.isTransactionInProgress().
Would a solution be to have the TransactionManagerAdapter#getStatus method delegate to
the TransactionAdapter#getStatus method?
Also see
http://forum.hibernate.org/viewtopic.php?t=966463
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira