This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I have the following Spring/Hibernate configuration. When I run it under WebLogic, it works fine. OFAPool is a connection pool defined in WebLogic.
However, I want to run Spring/Hibernate with my stand alone program. So I commented out the OFAPool for JndiObjectFactoryBean (since WebLogic is no longer involved), and then uncomment the second tag in the configuration below. I created a class called DevelopmentDriverManagerDataSource, which extends BasicDataSource. This will directly connect to my database.
However, when I run the stand-alone program, I got the below error. It seems that JtaTransactionManager is not set correctly. I don't understand why it works well using WebLogic's database connection pool, but not with stand-alone program. Please help. Thanks in advance.
Well, simply put, Weblogic has a JTATransactionManager that you are relying on, and when run stand-alone, you do not have one. Datasources do not provide the TransactionManager.
In your stand-alone configuration, why not change your transactionManager to the Spring TransactionManager. Actually, I thought if you use the Spring TransactionManager, it will just hook into whatever TransactionManager that is available in your environment. So in the case of Weblogic it hooks into JTA, on stand-alone, the Spring Framework provides its own.