Juergon has posted you do not need to use the TransactionProxyFactoryBean et al. if you leverage the support in Hibernate for Weblogic JTA. I have my session-per-transaction scope set-up using this approach with no Spring Transaction Manager. I just leverage Spring for the DAO and session support. Seems to work pretty good, especially now that I can lazy initialize my VOs, but I am experiencing some transactional problems per my post under the EJB category.
Originally Posted by Colin Sampaleanu
Hibernate property below:
<property name="hibernate.transaction.manager_lookup_class"> net.sf.hibernate.transaction.WeblogicTransactionManagerLookup