[hibernate-dev] JTA platform configuration: Hibernate OGM on WildFly

Scott Marlow smarlow at redhat.com
Tue Mar 29 11:17:36 EDT 2016



On 03/29/2016 10:29 AM, Sanne Grinovero wrote:
> When using Hibernate OGM on WildFly it's currently necessary to set
> this property:
>
>      hibernate.transaction.jta.platform = JBossAS
>
> 1 -- Would you all be ok for me to add a "WildFly" alias which
> resolves to the same implementation?

Sounds okay to me. :)

> This would be a patch for Hibernate ORM so it affects everyone.
> I'm not proposing (yet) to remove or deprecate the old value.
>
> 2 -- Could JipiJapa help so that end users don't need to set this?

Currently, the WildFly JipiJapa module for ORM 5.0 and the ORM 5.0 
module itself, have bidirectional 1-1 dependencies.

I think that ORM 5.0 may need some code changes to some of the 
integration/pu properties to be specified as class instances (in 
addition to allowing class names).  for example, [1] is specifying a 
class name for "hibernate.cache.region.factory_class", that ORM needs to 
be resolvable.

Even if ORM is changed to allow class instances to be passed in for all 
integration/pu properties, the JipiJapa module for ORM 5.0, still has a 
dependency on the ORM 5.0 classloader.  I suppose that OGM could also 
depends on the same ORM 5.0 classloader but that might be too big of a 
restriction for OGM (e.g. OGM might want to use a different version of 
ORM).

>
> We had plans for OGM support for JipiJapa, this could be a good time
> to refresh that idea?

 From a WildFly perspective, we do not yet have a branch for WildFly 11 
development.

Scott

[1] 
https://github.com/wildfly/wildfly/blob/master/jpa/hibernate5/src/main/java/org/jboss/as/jpa/hibernate5/HibernateSecondLevelCache.java#L62

>
> Thanks,
> Sanne
>


More information about the hibernate-dev mailing list