Probably in y'alls initiator you will need to make a specific interpretation of your various settings to determine whether to initiate the JTA-specific service. I think that as long as you don't trigger initialization of the Class, the JVM will not attempt to link in the JTA classes.
On Wed, Jan 14, 2015 at 3:39 AM, Emmanuel Bernard <emman...@hibernate.org> wrote: > > > On 14 Jan 2015, at 10:08, Gunnar Morling <gun...@hibernate.org> wrote: > > > > 2015-01-13 19:49 GMT+01:00 Steve Ebersole <st...@hibernate.org>: > > > >> You'd need to not specify the JtaPlatform service stuff. > >> > > > > Yes, but which org.hibernate.Transaction implementation to use? We'd > need a > > "fake" implementation which triggers the grid dialect upon > flush()/commit() > > invocations. > > I think I originally replaced it so that it worked for Infinispan. Which > mandates a JTA TM all the time (for transactions). > Looks like it was still working for the other datastores and no one > bothered to improve a working bit until you discovered the extra dependency > issue. _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
