there is no need for enable-welcome-root conf attribute anymore. Welcome page is disabled automatically when anything is deployed to '/' context.
We need to update that page to note it
With your configuration you should get your application bound to '/' only in case that your deployment is named exactly "railo01.war" otherwise it would not work.
if that does not work it is a bug, what exact version of WildFly do you use?
also you could add jboss-web.xml into your WEB-INF with content
I am running yesterdays nightly build - 8.0.0.Beta2-SNAPSHOT
I added C:\wildfly-8.0.0.Beta2-SNAPSHOT\bin\content\railo01.war\WEB-INF\jboss-web.xml with your content.
I did have this before with this as well
to match 'name' from standalone.xml
<host name="services.dev.am.com.au" alias="services.devam02.local" default-web-module="railo01.war" />
I have railo01.war deployed, and can access it at
But still no change.
I deliberately messed with the xml in jboss-web.xml - I was expecting to see eror messages
Where would these be logged?
How can I tell if jboss-web.xml is been read?
So which part of configure context-root did you not understand?
i am talking about context root, you are configuring virtual-host....
also why are you modifying content inside bin lib, that should be in standalone/deployments folder...
When I deploy a WAR (via web interface), that is where I found it.
If I drop the WAR file in
they also end up in
My jboss-web.xml is exactly how you described ( no virtual-host).
What do I have to do so I can but this file in
I have a similar problem. The essential question is "How do I set up a virtual host for a default WebApp at context root in WildFly"? Obviously the configuration differs from JBoss7.
Please update the documentation for WildFly (Admin Guide - WildFly 8 - Project Documentation Editor).
I got the virtual host with default web app at context root working on wildfly-8.0.0.Beta1 with the following configuration (the default-web-module attribute is supported again with beta1). I did not have to make changes regarding the "enable-welcome-root" flag.
Note: My browser played tricks with me and displayed the WildFly welcome page from cache, so F5 helped displaying my application after I configured WildFly and Apache the following way:
<http-listener name="default" max-post-size="10485760" socket-binding="http"/>
<ajp-listener name="myListener" socket-binding="ajp"/>
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<host name="my-virtual-host" alias="myapp.domain.org" default-web-module="mywebapp.war" />
<?xml version="1.0" encoding="UTF-8"?>
JkMount /* worker1
JkMount / worker1
What is the path to your 'jboss-web.xml' file?
Do you created it on the file system,
or should it be packaged within the WAR?
jboss-web.xml is located in the WEB-INF directory and packaged within the WAR
Makes sense, will try that.