<div dir="ltr">There's a proper transaction manager running in WF, maybe we should drop our stuff and use that instead. We can manage the transactions by retrieving the transaction manager from JNDI.</div><div class="gmail_extra"><br><div class="gmail_quote">On 8 August 2016 at 14:46, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On 8/8/16 8:31 AM, Marek Posolda wrote:<br>
> The question is, if we can fix liquibase instead of require people to<br>
> change DS? Maybe I can try to continue in your branch later this week<br>
> and look at it?<br>
><br>
<br>
</span>It's not just liquibase. J<br>
<span class=""><br>
> Another possibility: Don't bootstrap JTA automatically at<br>
> KeycloakSessionFactory.create(<wbr>) but instead do it just in HTTP<br>
> requests (in KeycloakSessionServletFilter ). Then liquibase bootstrap<br>
> won't be an issue?<br>
><br>
<br>
</span>JPA Model will also barf with the same error if a JTA transaction is<br>
started as we do local JPA transactions. So we have to have the<br>
datasource flag or change how we interact with EntityManagers.<br>
<div class="HOEnZb"><div class="h5"><br>
Bill<br>
______________________________<wbr>_________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/keycloak-dev</a><br>
</div></div></blockquote></div><br></div>