9:29 a.m.
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?
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?
We had plans for OGM support for JipiJapa, this could be a good time
to refresh that idea?
Thanks,
Sanne
9:50 a.m.
2016-03-29 16:29 GMT+02:00 Sanne Grinovero <sanne(a)hibernate.org>:
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?
This would be a patch for Hibernate ORM so it affects everyone.
I'm not proposing (yet) to remove or deprecate the old value.
Yeah, I was wondering the same when seeing your PR.
When is it required to be specified, though? Assuming 2. is done - in which
case would a user have to set the platform explicitly to that impl?
2 -- Could JipiJapa help so that end users don't need to set this?
We had plans for OGM support for JipiJapa, this could be a good time
to refresh that idea?
There is some awareness of OGM in JipiJapa already; I don't remember the
details, but when we changed the slot id for OGM a while ago, that required
an update in JipiJapa, too. Scott will know more.
For sure it would be great if specifying the JTA platform wasn't necessary
when using OGM on WF. I suppose it'd help to file a WFLY issue to capture
the discussion and required actions.
Thanks,
Sanne
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
10:25 a.m.
On 03/29/2016 10:50 AM, Gunnar Morling wrote:
2016-03-29 16:29 GMT+02:00 Sanne Grinovero <sanne(a)hibernate.org
<mailto:sanne@hibernate.org>>:
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?
This would be a patch for Hibernate ORM so it affects everyone.
I'm not proposing (yet) to remove or deprecate the old value.
Yeah, I was wondering the same when seeing your PR.
When is it required to be specified, though? Assuming 2. is done - in
which case would a user have to set the platform explicitly to that impl?
2 -- Could JipiJapa help so that end users don't need to set this?
We had plans for OGM support for JipiJapa, this could be a good time
to refresh that idea?
There is some awareness of OGM in JipiJapa already; I don't remember the
details, but when we changed the slot id for OGM a while ago, that
required an update in JipiJapa, too. Scott will know more.
We have some OGM support in the JPA (EE) container but not in the
JipiJapa module for ORM 5.0. The JPA container checks if the
persistence provider class is
"org.hibernate.ogm.jpa.HibernateOgmPersistence" and uses the
"org.hibernate.ogm:main" module if yes. The JPA container also allows
the DataSource to not be specified in the persistence.xml.
For sure it would be great if specifying the JTA platform wasn't
necessary when using OGM on WF. I suppose it'd help to file a WFLY issue
to capture the discussion and required actions.
Thanks,
Sanne
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org <mailto:hibernate-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
10:17 a.m.
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/ja...
Thanks,
Sanne
1:37 p.m.
On Tue, Mar 29, 2016 at 9:30 AM Sanne Grinovero <sanne(a)hibernate.org> 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?
+1
This would be a patch for Hibernate ORM so it affects everyone.
I'm not proposing (yet) to remove or deprecate the old value.
I'd actually be against removing the JBoss entries.
3194
days inactive
3194
days old
4 comments
4 participants
participants (4)
-
Gunnar Morling -
Sanne Grinovero -
Scott Marlow -
Steve Ebersole