On 12/12/2013 4:01 PM, ssilvert(a)redhat.com wrote:
On 12/12/2013 3:14 PM, Bill Burke wrote:
> Are you doing it like PL had it and specifying the WAR name?
It's the deployment name, which is usually the same as the WAR name.
It's the same idea as PL's subsystem. At deployment time, we
dynamically add everything you would normally need to specify inside the
I'm focusing on WildFly for now. Any ETA on when that will be ready?
Looks like Wildfly master has the latest Undertow. We're kind of
dependent on Wildfly beta 2 being released if we want to provide
anything in Alpha 1.
I can do EAP6 if you think it's a must-have. If we support EAP6
not be able to manage the subsystem from the Keycloak admin console.
The only way you would be able to do it is by editing
standalone.xml/domain.xml, or issuing CLI commands.
I think we would want some kind of subsystem for EAP so we can provide
some more centralized configuration and sharing of system resources.
With WildFly we will (hopefully) have CORS support and we can manage
subsystem from the Keycloak admin console.
Thanks for the explanation of the attributes. All that looks good.
I'm not sure what to do about the RestEasy client. How is creation and
sharing of the client done today?
Client is created per war deployment right now.
JBoss, a division of Red Hat