[
https://issues.jboss.org/browse/WFLY-8478?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-8478:
----------------------------------------
This is true, but we should be careful about simple advice to use
{allow-resource-service-restart=true}. That's a power user setting that should only be
used by people with a very clear understanding of the effects. It's not in any way a
"better reload".
In this case {allow-resource-service-restart=true} is likely more useful, since I
don't *think* bouncing the listener service will have widely cascading effects. But
any advice to use {allow-resource-service-restart=true} should always include some comment
on what the expected effects would be. The end user will very likely not have a clue and
an uneducated guess will likely be too optimistic by far.
BTW, I'm not arguing with rejecting this issue if there is no reasonable way to update
the service without a service restart. And I have reason to believe there is such a way.
My point is just about what message we send to end users.
Setting elytron ssl-context on undertow without reload
------------------------------------------------------
Key: WFLY-8478
URL:
https://issues.jboss.org/browse/WFLY-8478
Project: WildFly
Issue Type: Bug
Components: Security, Web (Undertow)
Reporter: Martin Choma
Assignee: Tomaz Cerar
Labels: user_experience
Please, allow setting of elytron ssl-context on undertow without reload.
{code}
[standalone@localhost:9990 /]
/subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=ssl-context,value=server)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)