I don't have a big problem with it, but I don't see the need to do it. Is it not just a convenience thing to be able to get it directly from the transaction object rather than having to get the separate transaction manager object?

On 25 July 2016 at 16:59, Bill Burke <bburke@redhat.com> wrote:

I want to simplify KeycloakTransaction interface a bit and remove the
getRolbackOnly, setRollbackOnly, and isActive and only have them within
KeycloakTransationManager. I may have to refactor existing components
to handle this. See any issues? All this is the continuous process of
simplying our SPIs to make them easier to implement.

Bill

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