[jboss-jira] [JBoss JIRA] (WFLY-3639) default-web-module doesn't work for non default host

Guruprasad Nagaraj (JIRA) issues at jboss.org
Thu Oct 30 06:59:35 EDT 2014


    [ https://issues.jboss.org/browse/WFLY-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016019#comment-13016019 ] 

Guruprasad Nagaraj commented on WFLY-3639:
------------------------------------------

The workaround with creating/editing and adding the virtual-hosts in boss-web.xml does not seem to work, in that, multiple virtual-host tags in jboss-web.xml create problems.

I tried this workaround for my scenario where two virtual hosts are served exactly with the same WAR files, with no context-root configuration.

In wildfly/standalone/configuration/standalone.xml:

<host name="domain1" alias="domain1.rootdomain.com">
    <location name="/" handler="welcome-content"/>
    <filter-ref name="server-header"/>
    <filter-ref name="x-powered-by-header"/>
</host>
<host name="domain2" alias="domain2.rootdomain.com">
    <location name="/" handler="welcome-content"/>
    <filter-ref name="server-header"/>
    <filter-ref name="x-powered-by-header"/>
</host>
In jboss-web.xml:

<jboss-web>
  <virtual-host>domain1</virtual-host>
  <virtual-host>domain2</virtual-host>
</jboss-web>
During deploy/redeploy Wildfly complains that already one virtual-host tag was processed and the deployment/redeployment fails.

Is there any other solution for this problem?

> default-web-module doesn't work for non default host
> ----------------------------------------------------
>
>                 Key: WFLY-3639
>                 URL: https://issues.jboss.org/browse/WFLY-3639
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 8.1.0.Final
>            Reporter: Tomaz Cerar
>            Assignee: Tomaz Cerar
>             Fix For: 9.0.0.Beta1
>
>
> If you use config like this:
> {code:xml}
> <host name="default-host" default-web-module="myapp1.war" alias="webapp.domain1.com"/>
>     <host name="other-host" default-web-module="myapp2.war" alias="test.domain2.net"/>
> {code}
> and have apps myapp1.war & myapp2.war deployed myappwar2.war won't be bind to other-host.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jboss-jira mailing list