bburke at redhat.com
Mon Jul 3 16:19:37 EDT 2017
Please see my response to your original problem.
On 7/3/17 12:16 PM, Dmitry wrote:
> At the moment, the ProviderFactory::postInit() method is not called
> during hot (re)deployment of providers, only during server startup.
> This is considered a bug (see discussion in keycloak-user, KEYCLOAK-
> 5131 and PR #4282).
> Meanwhile, Marek and I have been discussing the problem of accessing
> data model from postInit (see the keycloak-user post). Turns out that
> the semantics should be significantly different depending on whether
> postInit() is called during server startup or hot deploy. In the first
> case, one should listen for PostMigrationEvent. In the second case, the
> event is not available and thus shouldn't be listened for. However, the
> provider should be able to somehow distinguish the cases. There are
> some hacks like analyzing current thread name, querying JNDI or
> Resteasy, but maybe we can come up with something more clean and
> Marek has suggested that the new method should be introduced on the
> ProviderFactory interface, with empty default implementation (in order
> not to break the code). What do you think?
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
More information about the keycloak-dev