<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 18 January 2016 at 13:52, 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">
<div bgcolor="#FFFFFF" text="#000000">
I think we should support this. We also need to make sure deploying
these components also picks up things like EJBs, JPA, etc. For 2.0
we should probably consider using JTA too.</div></blockquote><div><br></div><div>+1 To everything, but for 2.x</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div><div class="h5"><br>
<br>
<div>On 1/18/2016 4:40 AM, Stian Thorgersen
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 18 January 2016 at 09:46, Travis
De Silva <span dir="ltr"><<a href="mailto:traviskds@gmail.com" target="_blank">traviskds@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I think the jar is a good idea. I have
hocked it up with our Jenkins CI process.
<div><br>
</div>
<div>As you mentioned, since the themes are cached, we
have no option but to restart KeyCloak. This might go
well in a non-clustered production environment.</div>
<div><br>
</div>
<div>I don't think wildfly modules are reloadable. But
wildfly allows you to deploy a jar just like a war.
Wondering why you guys didn't take that route and went
with the module route. </div>
<div><br>
</div>
<div>Also if there is anyway to clear the theme cache
when we deploy a new change without having to restart
KeyCloak would be great. I don't want to disable the
cache settings in keycloak-server.json as cache is
important for performance but just want a way to
reload it when we deploy new changes/new themes via
the jar file.</div>
</div>
</blockquote>
<div><br>
</div>
<div>The ideal would be to be able to hot-deploy both themes
and providers, but using modules is much easier. We could
probably extend the Keycloak subsystem to detect
deployment of theme jars as they contain a
keycloak-themes.json. Provider jars would be slightly
harder unless we add some marker file.</div>
<div><br>
</div>
<div>For themes you would have to clear the theme cache.
Again, this is something the subsystem could probably do
and it could automatically clear the cache for the themes
found in the deployed theme jar. To prevent browser caches
we'd also need some mechanism to do that. Currently
resources are versioned by the version of the server and
that's it. So if you change a resource it wouldn't be
updated in the users browser.</div>
<div><br>
</div>
<div>All nice to haves, but we don't have the resources ATM
to implement it.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div><br>
</div>
</div>
<div>
<div><br>
<div class="gmail_quote">
<div dir="ltr">On Mon, 18 Jan 2016 at 19:25 Stian
Thorgersen <<a href="mailto:sthorger@redhat.com" target="_blank">sthorger@redhat.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">You can chuck it into
standalone/configuration/themes for production
as well. The docs suggest to not do that as in
production you want a stable set of files and
make sure all nodes in a cluster has the same
versions. Themes are also by default cached,
both on the server side and in the browser.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 18 January 2016 at
08:59, Juraci Paixão Kröhling <span dir="ltr"><<a href="mailto:juraci@kroehling.de" target="_blank"></a><a href="mailto:juraci@kroehling.de" target="_blank">juraci@kroehling.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On
16.01.2016 23:29, Travis De Silva wrote:<br>
> I don't think wildfly does hot
deployment for modules.<br>
<br>
</span>How about adding/removing the module
via the Wildfly CLI?<br>
<br>
module add --name=the.theme...
--resources=...jar<br>
<br>
- Juca.<br>
<div>
<div>_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a></blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
keycloak-user mailing list
<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a></pre>
</blockquote>
<br>
</div></div><span class=""><pre cols="72">--
Bill Burke
JBoss, a division of Red Hat
<a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a></pre>
</span></div>
<br>_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br></blockquote></div><br></div></div>