Don't think so.  Anybody that has a 2nd datasource will now barf.  arjuna optimizes XA anyways is there is only one resource.

On 9/26/16 2:32 AM, Stian Thorgersen wrote:

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?

On 23 September 2016 at 21:31, Bill Burke <bburke@redhat.com> wrote:

The User Storage Provider SPI example uses a different datasource than
KeycloakDS.  What I found is that switching Keycloak to use JTA creates
a problem.  If you have 2 non-xa datasources in the same JTA
transaction, Wildfly barfs.  It doesn't allow it.  The workaround is
have only one non-xa datasources and have all the rest be xa
datasources, or to make them all be xa-datasources.

I'm changing the KeycloakDS to be an xa-datasource.  I don't think this
will effect anybody's application, although i'll need to note in
documentation that this is required and changed.


Bill

_______________________________________________
keycloak-dev mailing list
keycloak-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev