yes but the keycloak docs indicate that for production instances, to bundle the custom theme into a jar and then deploy it as a module. 

The hot deployment does not work when you deploy it as a module as indicated in the keycloak docs.

I don't think wildfly does hot deployment for modules. But wildfly also mentions that everything that is deployed such as war files, jar files are modules. Therefore instead of creating the standard wildfly module, I tried to deploy it as a standard jar deployment and then referred to that deployment name in keycloak-server.json but keycloak did not pick it up.



On Sun, 17 Jan 2016 at 01:43 Bill Burke <bburke@redhat.com> wrote:
Isn't there a theme directory in standalone/configuration?  I don't know if it is rechecked or not.


On 1/16/2016 8:11 AM, Travis De Silva wrote:
Hi,


You can bundle a theme into a jar and deploy it as a wildfly module.

This all works fine but the module is not hotdeployable. Whenever you do changes, you need to remove the module, then add it again and restart KeyCloak.

As you can imagine this is not ideal.

I trying to deploy the jar as a normal deployment as in Wildfly you can deploy jar file like you do war files. 

When you deploy like this, the module name is deployment.javafilename.jar

Then I added this name to the keycloak-server.json file but when I restart KeyCloak, it is not identifying the module.

Is there any other war where I can get my themes to reload once I redeploy the jar?

Note that as per the Keyclok docs, I disabled theme cache as well.

Cheers
Travis



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

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user