Allow optional tag virtual-host (and others) inside jboss-app.xml ----------------------------------------------------------------- Key: WFLY-7112 URL: https://issues.jboss.org/browse/WFLY-7112 Project: WildFly Issue Type: Feature Request Components: EE Affects Versions: 10.1.0.Final Reporter: Guido Jäkel Assignee: Jason Greene With undertow, the assignment of a web-application to a virtual host must be set in {{$WAR/META-INF/jboss-web.xml}}. A very adjacent parameter, the context-root, might be defined or overridden here, too. In practice, for a concrete deployment generally one have to adapt both parts of the URL, the (virtual) host and the context-root part and may use this file and e.g. apply it with the overlay feature. In case of an EAR, its components are declared inside {{$EAR/META-INF/application.xml}}. For an web application, the {{context-root}} is defined here. I found, that this have precedence to a {{$WAR/WEB-INF/jboss-web.xml}}. I don't expect this, but it might be defined by JEE specifications in that way. If not, this feature request should be converted to a bug report concerning a wrong preference order. To my knowledge, at the moment this file seems the only way to set the {{virtual-host}} to use. And this looks very inconsistent to me, because you have to use two different "far-out" files to controll this very associated informations. The informations in application.xml may be overridden and enriched by {{jboss-appl.xml}} in a similar manner as with {{web.xml}} and {{jboss-web.xml}}. I would expect (and suggest it as a feature) to define the virtual host here in an analogous way as the context root in {{application.xml}} may be overriden here. {code} <module> <web> <web-uri>a.war</web-uri> <context-root>/foo</context-root> <virtual-host>a.domain.tld</virtual-host> ... </web> </module> {code} This concept should be probably expanded to the complete feature set controlled by the {{jboss-web.xml}}, like undertow-related like {{server-instance}} or others like {{security-domain}}.