[Jboss-cvs] JBossAS SVN: r55863 - trunk/ejb3/src/resources/test-configs/ejb3-jacc/deploy/jbossweb-tomcat6.sar/META-INF
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Aug 14 03:38:30 EDT 2006
Author: wolfc
Date: 2006-08-14 03:38:27 -0400 (Mon, 14 Aug 2006)
New Revision: 55863
Added:
trunk/ejb3/src/resources/test-configs/ejb3-jacc/deploy/jbossweb-tomcat6.sar/META-INF/jboss-service.xml
Log:
default jboss-service.xml
Added: trunk/ejb3/src/resources/test-configs/ejb3-jacc/deploy/jbossweb-tomcat6.sar/META-INF/jboss-service.xml
===================================================================
--- trunk/ejb3/src/resources/test-configs/ejb3-jacc/deploy/jbossweb-tomcat6.sar/META-INF/jboss-service.xml 2006-08-14 07:38:20 UTC (rev 55862)
+++ trunk/ejb3/src/resources/test-configs/ejb3-jacc/deploy/jbossweb-tomcat6.sar/META-INF/jboss-service.xml 2006-08-14 07:38:27 UTC (rev 55863)
@@ -0,0 +1,174 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: jboss-service-all.xml 55263 2006-08-04 19:14:21Z dimitris at jboss.org $ -->
+<server>
+ <mbean code="org.jboss.web.tomcat.tc6.Tomcat6"
+ name="jboss.web:service=WebServer" xmbean-dd="META-INF/webserver-xmbean.xml">
+
+ <!-- You can configure a set of authenticators keyed by http-auth method used. This
+ will apply the same set of authenticators across all web applications. You can
+ override the set of authenticators at the web application level by adding
+ <authenticators> element to the respective jboss-web.xml -->
+ <!--
+ <attribute name="Authenticators" serialDataType="jbxb">
+ <java:properties xmlns:java="urn:jboss:java-properties"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
+ xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
+ <java:property>
+ <java:key>BASIC</java:key>
+ <java:value>org.apache.catalina.authenticator.BasicAuthenticator</java:value>
+ </java:property>
+ <java:property>
+ <java:key>CLIENT-CERT</java:key>
+ <java:value>org.apache.catalina.authenticator.SSLAuthenticator</java:value>
+ </java:property>
+ <java:property>
+ <java:key>DIGEST</java:key>
+ <java:value>org.apache.catalina.authenticator.DigestAuthenticator</java:value>
+ </java:property>
+ <java:property>
+ <java:key>FORM</java:key>
+ <java:value>org.apache.catalina.authenticator.FormAuthenticator</java:value>
+ </java:property>
+ <java:property>
+ <java:key>NONE</java:key>
+ <java:value>org.apache.catalina.authenticator.NonLoginAuthenticator</java:value>
+ </java:property>
+ </java:properties>
+ </attribute>
+ -->
+
+ <!-- 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">false</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.tc6.session.JBossCacheManager
+ -->
+ <attribute name="ManagerClass">
+ org.jboss.web.tomcat.tc6.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 at the end of requests. In this case, the
+ "SnapshotInterval" attribute is not used.
+ The "interval" mode, in association with the "SnapshotInterval"
+ attribute, indicates that modified sessions will only be replicated
+ every "SnapshotInterval" milliseconds at most.
+
+ Note that this attribute is not in effect if the replication-granularity
+ is set to FIELD. If it is FIELD, it will be per http request (that is,
+ "instant" mode.)
+ -->
+ <attribute name="SnapshotMode">instant</attribute>
+ <!-- you may switch to "interval" -->
+ <attribute name="SnapshotInterval">2000</attribute>
+
+ <!--
+ Whether to use MOD_JK(2) for load balancing with sticky session
+ combined with JvmRoute. If set to true, it will insert a JvmRouteValve
+ 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>
+
+ <!-- Depends on the Authorization Manager Service-->
+ <depends optional-attribute-name="AuthorizationManagerService"
+ proxy-type="attribute">jboss.security:service=AuthorizationManager
+ </depends>
+
+ <!-- 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>
+
+ <!--
+ Needed if using HTTP Session Clustering or if the
+ ClusteredSingleSignOn valve is enabled in the tomcat server.xml file
+ -->
+ <depends>jboss.cache:service=TomcatClusteringCache</depends>
+
+ <depends>jboss:service=TransactionManager</depends>
+
+ <!-- Only needed if the org.jboss.web.tomcat.tc6.jca.CachedConnectionValve
+ is enabled in the tomcat server.xml file.
+ -->
+ <depends>jboss.jca:service=CachedConnectionManager</depends>
+
+ </mbean>
+
+</server>
+
More information about the jboss-cvs-commits
mailing list