bcalmac wrote:
Thanks Michel for the quick response. I was setting the property jta.UserTransaction instead of hibernate.transaction.manager_lookup_class. Setting the second works flawlessly.
I was trying to avoid appserver specific info in the hibernate config, but it's not such a big deal.
What about the second question? Is it OK not to use the transaction object at all? The transaction objects is useful when you want to have multiple transactions in the same session, but is it required even for just one transaction?
Thank you.
Following is the configuration:
<!-- Transaction API -->
<property name="transaction.factory_class">net.sf.hibernate.transaction.JTATransactionFactory
</property>
<property name="transaction.manager_lookup_class">
net.sf.hibernate.transaction.WebSphereTransactionManagerLookup
</property>
but getting following error:
[10/23/04 15:58:34:356 AST] 6a2dede1 JTATransactio E net.sf.hibernate.transaction.JTATransaction TRAS0014I: The following exception was logged javax.naming.NameNotFoundException: Name "comp/UserTransaction" not found in context "java:".