<div dir="ltr">Can't we just leave it as is and document if someone does indeed have a custom provider with a separate datasource they need to change it?</div><div class="gmail_extra"><br><div class="gmail_quote">On 23 September 2016 at 21:31, 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">The User Storage Provider SPI example uses a different datasource than<br>
KeycloakDS. What I found is that switching Keycloak to use JTA creates<br>
a problem. If you have 2 non-xa datasources in the same JTA<br>
transaction, Wildfly barfs. It doesn't allow it. The workaround is<br>
have only one non-xa datasources and have all the rest be xa<br>
datasources, or to make them all be xa-datasources.<br>
<br>
I'm changing the KeycloakDS to be an xa-datasource. I don't think this<br>
will effect anybody's application, although i'll need to note in<br>
documentation that this is required and changed.<br>
<br>
<br>
Bill<br>
<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>
</blockquote></div><br></div>