[
https://issues.jboss.org/browse/WFLY-8538?page=com.atlassian.jira.plugin....
]
Jan Stourac commented on WFLY-8538:
-----------------------------------
I've updated issue description to make more obvious what is going on here.
Also, I wanted to created another jira to at least mark 'default-virtual-host'
attribute as deprecated to prepare for its possible removal in the future. Although, the
truth is that it is still necessary for correct behavior and configuration of the server
:/ . Not sure whether it is reasonable to mark it as deprecated in such case... Please
raise your voice here.
Remove need to configure default-virtual-host at subsystem level
----------------------------------------------------------------
Key: WFLY-8538
URL:
https://issues.jboss.org/browse/WFLY-8538
Project: WildFly
Issue Type: Enhancement
Components: Web (Undertow)
Affects Versions: 11.0.0.Alpha1
Reporter: Radim Hatlapatka
Assignee: Stuart Douglas
Priority: Major
There is currently needed host to which the deployments should be deployed by default.
This is found out from default-virtual-host at undertow subsystem level. This value
actually duplicates setting from the value set in default-host attribute of default
server, as such it should be removed and thus config simplified by counting the needed
value default server's default-host value.
Summing it up:
current behavior:
* default server value is determined by: {{/subsystem=undertow\[default-server\]}}
attribute
* default virtual host value is determined by:
{{/subsystem=undertow\[default-virtual-host\]}} attribute
proposed behavior:
* default server value is determined by: {{/subsystem=undertow\[default-server\]}}
attribute (*no change here*)
* default virtual host value is determined by:
{{/subsystem=undertow/server=VALUE_DETERMINED_IN_PREVIOUS_STEP\[default-host\]}}
attribute
* deprecate {{/subsystem=undertow\[default-virtual-host\]}} attribute and remove it
completely in some of upcoming versions
CC [~ctomc]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)