Re: [hibernate-dev] Breaking JBossStandAloneJtaPlatform backwards compatibility

2018-05-27 Thread Sanne Grinovero
On 27 May 2018 at 00:30, Scott Marlow wrote: > Next idea, we should first look for the WFTC classes, if not found, then > look for Arjuna classes. +1 that would be nice and I see other implementations e.g. JBossAppServerJtaPlatform have a precedent of attempting multiple strategies to maintain ba

Re: [hibernate-dev] Breaking JBossStandAloneJtaPlatform backwards compatibility

2018-05-27 Thread Scott Marlow
On Sun, May 27, 2018 at 8:17 AM, Sanne Grinovero wrote: > On 27 May 2018 at 00:30, Scott Marlow wrote: > > Next idea, we should first look for the WFTC classes, if not found, then > > look for Arjuna classes. > > +1 that would be nice and I see other implementations e.g. > JBossAppServerJtaPlatf

Re: [hibernate-dev] Breaking JBossStandAloneJtaPlatform backwards compatibility

2018-05-27 Thread Sanne Grinovero
On 27 May 2018 at 15:29, Scott Marlow wrote: > > > On Sun, May 27, 2018 at 8:17 AM, Sanne Grinovero > wrote: >> >> On 27 May 2018 at 00:30, Scott Marlow wrote: >> > Next idea, we should first look for the WFTC classes, if not found, then >> > look for Arjuna classes. >> >> +1 that would be nice

Re: [hibernate-dev] Breaking JBossStandAloneJtaPlatform backwards compatibility

2018-05-27 Thread Steve Ebersole
JBossStandalone is meant for use of JBoss Transactions outside of WildFly. Why are we using it inside WildFly. Inside WildFly, jipijapa ought to be defining that however it needs through a custom JtaPlatform and probably the JtaPlatformInitiator. On Sun, May 27, 2018, 3:58 PM Sanne Grinovero wr