The context-root jboss-web.xml element discussed (I guess too briefly)
in chap 9 is the answer:

The context-root element allows one to specify the prefix under which web application is located. This is only applicable to stand-alone web application deployment as a WAR file. Web applications included as part of an EAR must set the root using the context-root element of the EAR application.xml descriptor.

example jboss-jmx-console.war/WEB-INF/jboss-web.xml:

<jboss-web>
        <!-- An emtpy context-root signifies the default root context -->
        <context-root />
</jboss-web>

--
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

Robert Cauble wrote:

If I take jboss 3.2.2 out-of-the-box and rename server/default/deploy/jmx-console.war to ROOT.war and I try going to the url

http://localhost:8080 <http://localhost:8080/> I get a “HTTP Status 500 – No Content configured to process this request” response.



I can then go to http://localhost:8080/ROOT and it works fine (goes to the jmx console as expected). What is the additional configuration I need to do in order to define a root context? I couldn’t find anything in the JBoss documentation which we purchased which describes how to do this.



Any pointers here would be greatly appreciated.



Thanks,

Rob




------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to