Solution : Way 1

Under you war (unzipped when deployed), in file "myProject\WebContent\WEB-INF\jboss-web.xml"

<?xml version="1.0" encoding="UTF-8"?>
<!-- -->
<jboss-web xmlns=""

With your backoffice, write in this unzipped deployed war, to serve static files.

Solution : Way 2

Adding allowLinking="true" in Jboss context (C:\jboss-6.1.0.Final\server\default\deploy\jbossweb.sar\context.xml)

<Context cookies="true" crossContext="true" allowLinking="true">

or only in your project (DeployedProject\WebContent\WEB-INF\context.xml)

<Context allowLinking="false">

All others context (with or not vhost) inherit the attribute allowLinking="true" and the symbolic link is working inside my DeployedProject.war/mySymLink

Adding the system symbolic link : DeployedProject.war/mySymLink linked to /tmp

DeployedProject.war# ln -s /tmp mySymLink

Now, you can access to http://localhost:8080/DeployedProject/mySymLink/myPicture.jpg and myPicture.jpg is stored in /tmp/myPicture.jpg

Enjoy, and if you can solve this problem without symlink...

An alternative way to returning files outside war, seem to be using a servlet, for get and return external file system... not try, but exemples in followings links.

External Static Directories Ressources

  • jbossweb
  • The Resources Component The Resources element represents the web application static resources, from which classes will be loaded, HTML, JSP and the other static files will be served. Note: Running a webapp with non-filesystem based Resources implementations is only possible when the webapp does not rely on direct filesystem access to its own resources, and uses the methods in the ServletContext interface to access them.
  • The Context Container The Context element represents a web application, which is run within a particular virtual host.
    • docBase : The Document Base (also known as the Context Root) directory for this web application, or the pathname to the web application archive file (if this web application is being executed directly from the WAR file). You may specify an absolute pathname for this directory or WAR file, or a pathname that is relative to the appBase directory of the owning Host.
    • path : The context path of this web application, which is matched against the beginning of each request URI to select the appropriate web application for processing. All of the context paths within a particular Host must be unique. If you specify a context path of an empty string (""), you are defining the default web application for this Host, which will process all requests not assigned to other Contexts. The value of this field must not be set except when statically defining a Context in server.xml, as it will be inferred from the filenames used for either the .xml context file or the docBase.
    • The JBoss 4 Application Server Web Developer Reference : JBoss AS 4.0.5
    • The server.xml file
    • Setting the context root of a web application
    • Setting up Virtual Hosts
    • Serving Static Content
    • The JBoss 4 Application Server Guide : JBoss AS 4.0.3
    • Web Applications
      • Serving Static Content: JBoss provides a default application that serves content for the root application context. This default context is the ROOT.war application in the jbossweb-tomcat50.sar directory. You can serve static files not associated with any other application by adding that content to the ROOT.war directory. For example, if you want to have a shared image directory you could create an image subdirectory inside of ROOT.war and place the images there. You could then access an image named myimage.jpg at http://localhost:8080/images/myimage.jpg.

Which tomcat is embedded in jboss6

With jboss-6.1.0.Final, headers are :

Server	Apache-Coyote/1.1
X-Powered-By	Servlet/3.0; JBossAS-6

On failure page, signature are :

JBoss Web/3.0.0-CR2

Jmx console

  • http://localhost:8080/jmx-console/
    • jboss.web
      • J2EEApplication=none,J2EEServer=none,j2eeType=WebModule,name=//localhost/Test6
	The document root for this web application

	Performance statistics support for this managed object
( )True (X)False   

	Name of the engine domain, if different from the context domain
Type of the modeled resource. Can be set only once

(X)True ( )False   

The welcome files for this context

staticResources (
Static resources associated with the context.

The context path for this Context

 Test6  index.html index.htm index.jsp default.html default.htm default.jsp 
String deployment descriptor

( )True (X)False 
	The DefaultContext override flag for this web application
(X)True ( )False   
	Should we cache static resources for this webapp
namingContextListener (org.apache.catalina.core.NamingContextListener) Cannot find getter method getNamingContextListener
	Associated naming context listener.
( )True (X)False 
	Access to tomcat internals
( )True (X)False 
	Allow symlinking to outside the webapp root directory, if the webapp is an exploded directory
Trying to change any value return : "An error has occurred."
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console].[HtmlAdaptor]] (http- "Servlet.service()" pour la servlet HtmlAdaptor a généré une exception: java.lang.NoSuchMethodException: org.apache.catalina.core.StandardContext.setEventProvider(boolean)



Listener Valve Alias Realm

  • apache-tomcat-6.0.26-src » org.apache » catalina » storeconfig » StandardHostSF
       * Store the specified Host properties and childs
       * (Listener,Alias,Realm,Valve,Cluster, Context)