持久性单元,不同的hibernate.transaction.manager_lookup_class属性 [英] persistence-unit, different hibernate.transaction.manager_lookup_class property

查看:181
本文介绍了持久性单元,不同的hibernate.transaction.manager_lookup_class属性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有Java EE应用程序,而且我的EJB模块有 persistence.xml

我在3个应用程序服务器上部署我的应用程序:JBoss,GlassFish和WebLogic,并且每个服务器都需要自己的 hibernate.transaction.manager_lookup_class b
$ < property name =transaction.manager_lookup_classvalue = org.hibernate.transaction.WeblogicTransactionManagerLookup/>

JBoss需要

 < property name =transaction.manager_lookup_classvalue =org.hibernate.transaction.JBossTransactionManagerLookup/> 

玻璃鱼

 < property name =transaction.manager_lookup_class
value =org.hibernate.transaction.SunONETransactionManagerLookup/>

最好的方法是什么?

解决方案

解决方案是使用

 < property name =hibernate.transaction。 factory_classvalue =org.hibernate.transaction.JTATransactionFactory/> 

而不是

 < property name =transaction.manager_lookup_class


I have Java EE application, and my EJB module have persistence.xml.

I deploy my app on 3 app servers: JBoss, GlassFish and WebLogic, and every server needs own hibernate.transaction.manager_lookup_class property.
WL needs

<property name="transaction.manager_lookup_class" value="org.hibernate.transaction.WeblogicTransactionManagerLookup" /> 

JBoss needs

<property name="transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup" />  

Glass fish

<property name="transaction.manager_lookup_class"    
value="org.hibernate.transaction.SunONETransactionManagerLookup" />  

What is the best way to do this?

解决方案

Solution is use

<property name="hibernate.transaction.factory_class" value="org.hibernate.transaction.JTATransactionFactory"/>  

instead of

<property name="transaction.manager_lookup_class"

这篇关于持久性单元,不同的hibernate.transaction.manager_lookup_class属性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆