wood burning stoves 2.0*
The moose likes BEA/Weblogic and the fly likes Standalone java app - JNDI lookup on weblogic server - Spring/Hibernate/JTA not committing to DB Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Standalone java app - JNDI lookup on weblogic server - Spring/Hibernate/JTA not committing to DB" Watch "Standalone java app - JNDI lookup on weblogic server - Spring/Hibernate/JTA not committing to DB" New topic
Author

Standalone java app - JNDI lookup on weblogic server - Spring/Hibernate/JTA not committing to DB

Nickolas Case
Ranch Hand

Joined: Apr 26, 2008
Posts: 98
Hello all!

I have been racking my brain for the last few days trying to convert a standalone java application from a standard database connection to a JNDI lookup on a weblogic server and I can't seem to get it to work.

applicationContext.xml follows:



persistence.xml:



I apologize if this isn't the correct forum.

Nickolas Case
Ranch Hand

Joined: Apr 26, 2008
Posts: 98
I solved my issue. I hadn't implemented JTA correctly and I didn't need to. After I reverted my code to JNDI lookup and added the following jars my code worked.

com.bea.core.diagnostics.instrumentor_1.0.1.0.jar
com.bea.core.repackaged.asm_1.5.2.jar
com.bea.core.xml.beaxmlbeans_2.2.0.0


Of course, you'll still need the wlfullclient.jar using the jarbuilder.

Also, you don't want weblogic.jar along with wlfullclient.jar as this can cause errors too.

Cheers!
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Standalone java app - JNDI lookup on weblogic server - Spring/Hibernate/JTA not committing to DB