Jboss虚拟目录配置

%JBOSS_HOME%/server/default/deploy/jboss-web.deployer/server.xml

<Host name="localhost" 
            autoDeploy="false" deploy deployXML="false"> 
            <!-- Uncomment to enable request dumper. This Valve "logs interesting 
                 contents from the specified Request (before processing) and the 
                 corresponding Response (after processing). It is especially useful 
                 in debugging problems related to headers and cookies." 
            --> 
            <!-- 
            <Valve className="org.apache.catalina.valves.RequestDumperValve" /> 
            --> 

            <!-- Access logger --> 
            <!-- 
            <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve" 
                prefix="localhost_access_log." suffix=".log" 
                pattern="common" directory="${jboss.server.home.dir}/log" 
                resolveHosts="false" /> 
            --> 
            <!-- Uncomment to enable single sign-on across web apps 
deployed to this host. Does not provide SSO across a cluster.     
             
                If this valve is used, do not use the JBoss ClusteredSingleSignOn 
                valve shown below. 
             --> 
            <!-- 
            <Valve className="org.apache.catalina.authenticator.SingleSignOn" /> 
            --> 
            <!-- Uncomment to enable single sign-on across web apps 
               deployed to this host AND to all other hosts in the cluster 
               with the same virtual hostname. 
             
               If this valve is used, do not use the standard Tomcat SingleSignOn 
               valve shown above. 
             
               This valve uses JGroups to communicate across the cluster. The 
               JGroups Channel used for this communication can be configured 
               by editing the "sso-channel.xml" file found in the same folder 
               as this file. If this valve is running on a machine with multiple 
               IP addresses, configuring the "bind_addr" property of the JGroups 
               UDP protocol may be necessary. Another possible configuration 
               change would be to enable encryption of intra-cluster communications. 
               See the sso-channel.xml file for more details. 
             
               Besides the attributes supported by the standard Tomcat 
SingleSignOn valve (see the Tomcat docs), this version also supports 
               the following attribute: 
             
               partitionName     the name of the cluster partition in which 
                                 this node participates. If not set, the default 
                                 value is "sso-partition/" + the value of the 
                                 "name" attribute of the Host element that 
                                 encloses this element (e.g. "sso-partition/localhost") 
            --> 
            <!-- 
            <Valve className="org.jboss.web.tomcat.tc5.sso.ClusteredSingleSignOn" /> 
            --> 
         
            <!-- Uncomment to check for unclosed connections and transaction terminated checks 
                 in servlets/jsps. 
                 Important: You need to uncomment the dependency on the CachedConnectionManager 
                            in META-INF/jboss-service.xml 
            <Valve className="org.jboss.web.tomcat.tc5.jca.CachedConnectionValve" 
                cachedC 
                transacti /> 
            --> 
                         <!--部署虚拟目录-->
          <!-- <Context path="/test" docBase="E:\StudyWork\lianlianAward\WebRoot" reloadable="true" debug="0"> </Context>     
--></Host>