Index: lams_build/conf/unix/jboss/tomcat/jboss-service.xml
===================================================================
diff -u
--- lams_build/conf/unix/jboss/tomcat/jboss-service.xml	(revision 0)
+++ lams_build/conf/unix/jboss/tomcat/jboss-service.xml	(revision ba9f5b8aecb7f4180d04b884626c4ff8f3b18f1d)
@@ -0,0 +1,138 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id$ -->
+
+<server>
+
+   <mbean code="org.jboss.web.tomcat.tc5.Tomcat5"
+      name="jboss.web:service=WebServer">
+
+      <!-- The JAAS security domain to use in the absense of an explicit
+      security-domain specification in the war WEB-INF/jboss-web.xml
+      -->
+      <attribute name="DefaultSecurityDomain">java:/jaas/other</attribute>
+
+      <!-- Get the flag indicating if the normal Java2 parent first class
+           loading model should be used over the servlet 2.3 web container first
+           model.
+      -->
+      <attribute name="Java2ClassLoadingCompliance">false</attribute>
+      <!-- A flag indicating if the JBoss Loader should be used. This loader
+           uses a unified class loader as the class loader rather than the tomcat
+           specific class loader.
+           The default is false to ensure that wars have isolated class loading
+           for duplicate jars and jsp files.
+      -->
+      <attribute name="UseJBossWebLoader">true</attribute>
+      <!-- The list of package names that should not be loaded without
+         delegating to the parent class loader before trying the web app
+         class loader. The packages listed here are those tha are used by
+         the web container implementation and cannot be overriden.
+         This only applies when UseJBossWebLoader=false.
+      -->
+      <attribute name="FilteredPackages">org.apache.commons.logging</attribute>
+
+      <attribute name="LenientEjbLink">true</attribute>
+
+      <!--
+          Class of the session manager (used if context is marked as 'distributable'. Currently allowed values:
+          - org.jboss.web.tomcat.tc5.session.JBossCacheManager
+      -->
+      <attribute name="ManagerClass">org.jboss.web.tomcat.tc5.session.JBossCacheManager</attribute>
+
+      <!-- The name of the request attribute under with the authenticated JAAS
+      Subject is stored on successful authentication. If null or empty then
+      the Subject will not be stored.
+      -->
+      <!--
+      <attribute name="SubjectAttributeName">j_subject</attribute>
+      -->
+
+      <!-- The SessionIdAlphabet is the set of characters used to create a session Id
+           It must be made up of exactly 65 unique characters
+      <attribute name="SessionIdAlphabet">ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+-*</attribute>
+      -->
+
+      <!--
+        *******************************************************
+        ****************** CLUSTERING *************************
+        *******************************************************
+        In order to activate HTTP Session clustering for Tomcat
+        make sure you run JBoss's "all" configuration i.e.
+        "run -c all"
+        (the default configuration doesn't contain clustering)
+
+        Furthermore, you may change SnapshotMode and
+        SnapshotInterval attributes below to indicate when to
+        synchronize changes with the other node(s).
+
+        If you use Apache+mod_jk(2) you will most probably use
+        the AJP1.3 connector below. Thus, if you so wish,
+        you may comment (i.e. deactivate) the HTTP connector
+        as it won't be used anymore.
+
+        *******************************************************
+        *******************************************************
+        *******************************************************
+       -->
+
+      <!--
+        If you are using clustering, the following two attributes
+        define when the sessions are replicated to the other nodes.
+        The default value, "instant", synchronously replicates changes
+        to the other nodes. In this case, the "SnapshotInterval" attribute
+        is not used.
+        The "interval" mode, in association with the "SnapshotInterval"
+        attribute, indicates that Tomcat will only replicates modified
+        sessions every "SnapshotInterval" miliseconds at most.
+      -->
+      <attribute name="SnapshotMode">instant</attribute> <!-- you may switch to "interval" -->
+      <attribute name="SnapshotInterval">2000</attribute>
+      <!-- A flag indicating if the local vm session value should be used if
+      it exists. When true, the existing vm local session values are used and
+      updates are replicated, but updates to the same session on other nodes
+      do not update the local session value. This mode is only useful for
+      failover. When false, the session value is obtained from the distributed
+      cache. This mode can be used with load balancing.
+      -->
+      <attribute name="UseLocalCache">true</attribute>
+
+      <!--
+      Whether to use MOD_JK(2) for load balancing with sticky session 
+      combined with JvmRoute. If set to true, it will insert a JvmRouteFilter 
+      to intercept every request and replace the JvmRoute if it detects a 
+      failover. In addition, you will need to set the JvmRoute inside
+      Tomcat, e.g.,
+        Engine name="jboss.web" jmvRoute="Node1" defaultHost="localhost" 
+      in server.xml.
+
+      For clustering purpose only.
+      -->
+      <attribute name="UseJK">false</attribute>
+
+      <attribute name="Domain">jboss.web</attribute>
+
+      <!-- A mapping to the server security manager service which must be
+      operation compatible with type
+      org.jboss.security.plugins.JaasSecurityManagerServiceMBean. This is only
+      needed if web applications are allowed to flush the security manager
+      authentication cache when the web sessions invalidate.
+      -->
+      <depends optional-attribute-name="SecurityManagerService"
+         proxy-type="attribute">jboss.security:service=JaasSecurityManager
+      </depends>
+
+      <!--
+         Configuration for HTTP Session Clustering using JBossCache
+      -->
+      <!--
+      <depends>jboss.cache:service=TomcatClusteringCache</depends>
+      -->
+      <depends>jboss:service=TransactionManager</depends>
+      <!-- Only needed if the org.jboss.web.tomcat.tc5.jca.CachedConnectionValve
+      is enabled in the tomcat server.xml file
+      <depends>jboss.jca:service=CachedConnectionManager</depends>
+      -->
+   </mbean>
+
+</server>
+
Index: lams_build/conf/windows/jboss/tomcat/jboss-service.xml
===================================================================
diff -u
--- lams_build/conf/windows/jboss/tomcat/jboss-service.xml	(revision 0)
+++ lams_build/conf/windows/jboss/tomcat/jboss-service.xml	(revision ba9f5b8aecb7f4180d04b884626c4ff8f3b18f1d)
@@ -0,0 +1,138 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id$ -->
+
+<server>
+
+   <mbean code="org.jboss.web.tomcat.tc5.Tomcat5"
+      name="jboss.web:service=WebServer">
+
+      <!-- The JAAS security domain to use in the absense of an explicit
+      security-domain specification in the war WEB-INF/jboss-web.xml
+      -->
+      <attribute name="DefaultSecurityDomain">java:/jaas/other</attribute>
+
+      <!-- Get the flag indicating if the normal Java2 parent first class
+           loading model should be used over the servlet 2.3 web container first
+           model.
+      -->
+      <attribute name="Java2ClassLoadingCompliance">false</attribute>
+      <!-- A flag indicating if the JBoss Loader should be used. This loader
+           uses a unified class loader as the class loader rather than the tomcat
+           specific class loader.
+           The default is false to ensure that wars have isolated class loading
+           for duplicate jars and jsp files.
+      -->
+      <attribute name="UseJBossWebLoader">true</attribute>
+      <!-- The list of package names that should not be loaded without
+         delegating to the parent class loader before trying the web app
+         class loader. The packages listed here are those tha are used by
+         the web container implementation and cannot be overriden.
+         This only applies when UseJBossWebLoader=false.
+      -->
+      <attribute name="FilteredPackages">org.apache.commons.logging</attribute>
+
+      <attribute name="LenientEjbLink">true</attribute>
+
+      <!--
+          Class of the session manager (used if context is marked as 'distributable'. Currently allowed values:
+          - org.jboss.web.tomcat.tc5.session.JBossCacheManager
+      -->
+      <attribute name="ManagerClass">org.jboss.web.tomcat.tc5.session.JBossCacheManager</attribute>
+
+      <!-- The name of the request attribute under with the authenticated JAAS
+      Subject is stored on successful authentication. If null or empty then
+      the Subject will not be stored.
+      -->
+      <!--
+      <attribute name="SubjectAttributeName">j_subject</attribute>
+      -->
+
+      <!-- The SessionIdAlphabet is the set of characters used to create a session Id
+           It must be made up of exactly 65 unique characters
+      <attribute name="SessionIdAlphabet">ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+-*</attribute>
+      -->
+
+      <!--
+        *******************************************************
+        ****************** CLUSTERING *************************
+        *******************************************************
+        In order to activate HTTP Session clustering for Tomcat
+        make sure you run JBoss's "all" configuration i.e.
+        "run -c all"
+        (the default configuration doesn't contain clustering)
+
+        Furthermore, you may change SnapshotMode and
+        SnapshotInterval attributes below to indicate when to
+        synchronize changes with the other node(s).
+
+        If you use Apache+mod_jk(2) you will most probably use
+        the AJP1.3 connector below. Thus, if you so wish,
+        you may comment (i.e. deactivate) the HTTP connector
+        as it won't be used anymore.
+
+        *******************************************************
+        *******************************************************
+        *******************************************************
+       -->
+
+      <!--
+        If you are using clustering, the following two attributes
+        define when the sessions are replicated to the other nodes.
+        The default value, "instant", synchronously replicates changes
+        to the other nodes. In this case, the "SnapshotInterval" attribute
+        is not used.
+        The "interval" mode, in association with the "SnapshotInterval"
+        attribute, indicates that Tomcat will only replicates modified
+        sessions every "SnapshotInterval" miliseconds at most.
+      -->
+      <attribute name="SnapshotMode">instant</attribute> <!-- you may switch to "interval" -->
+      <attribute name="SnapshotInterval">2000</attribute>
+      <!-- A flag indicating if the local vm session value should be used if
+      it exists. When true, the existing vm local session values are used and
+      updates are replicated, but updates to the same session on other nodes
+      do not update the local session value. This mode is only useful for
+      failover. When false, the session value is obtained from the distributed
+      cache. This mode can be used with load balancing.
+      -->
+      <attribute name="UseLocalCache">true</attribute>
+
+      <!--
+      Whether to use MOD_JK(2) for load balancing with sticky session 
+      combined with JvmRoute. If set to true, it will insert a JvmRouteFilter 
+      to intercept every request and replace the JvmRoute if it detects a 
+      failover. In addition, you will need to set the JvmRoute inside
+      Tomcat, e.g.,
+        Engine name="jboss.web" jmvRoute="Node1" defaultHost="localhost" 
+      in server.xml.
+
+      For clustering purpose only.
+      -->
+      <attribute name="UseJK">false</attribute>
+
+      <attribute name="Domain">jboss.web</attribute>
+
+      <!-- A mapping to the server security manager service which must be
+      operation compatible with type
+      org.jboss.security.plugins.JaasSecurityManagerServiceMBean. This is only
+      needed if web applications are allowed to flush the security manager
+      authentication cache when the web sessions invalidate.
+      -->
+      <depends optional-attribute-name="SecurityManagerService"
+         proxy-type="attribute">jboss.security:service=JaasSecurityManager
+      </depends>
+
+      <!--
+         Configuration for HTTP Session Clustering using JBossCache
+      -->
+      <!--
+      <depends>jboss.cache:service=TomcatClusteringCache</depends>
+      -->
+      <depends>jboss:service=TransactionManager</depends>
+      <!-- Only needed if the org.jboss.web.tomcat.tc5.jca.CachedConnectionValve
+      is enabled in the tomcat server.xml file
+      <depends>jboss.jca:service=CachedConnectionManager</depends>
+      -->
+   </mbean>
+
+</server>
+