[jboss-cvs] JBossAS SVN: r61398 - in trunk/testsuite/src/resources/test-configs: jacc/deployers/jbossweb.deployer and 8 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sat Mar 17 13:26:46 EDT 2007
Author: scott.stark at jboss.org
Date: 2007-03-17 13:26:46 -0400 (Sat, 17 Mar 2007)
New Revision: 61398
Added:
trunk/testsuite/src/resources/test-configs/jacc/deployers/jbossweb.deployer/
trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb.deployer/
trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb.deployer/META-INF/war-deployers-beans.xml
trunk/testsuite/src/resources/test-configs/tomcat-ssl/deployers/jbossweb.deployer/
trunk/testsuite/src/resources/test-configs/tomcat-webctx/deployers/jbossweb.deployer/
trunk/testsuite/src/resources/test-configs/tomcat-webctx/deployers/jbossweb.deployer/META-INF/
trunk/testsuite/src/resources/test-configs/tomcat-webctx/deployers/jbossweb.deployer/META-INF/war-deployer-beans.xml
trunk/testsuite/src/resources/test-configs/webservice-ssl/deployers/jbossweb.deployer/
Removed:
trunk/testsuite/src/resources/test-configs/jacc/deployers/jbossweb-tomcat6.sar/
trunk/testsuite/src/resources/test-configs/jacc/deployers/jbossweb.deployer/META-INF/
trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb-tomcat6.sar/
trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb.deployer/META-INF/jboss-service.xml
trunk/testsuite/src/resources/test-configs/tomcat-ssl/deployers/jbossweb-tomcat6.sar/
trunk/testsuite/src/resources/test-configs/tomcat-ssl/deployers/jbossweb.deployer/META-INF/jboss-service.xml
trunk/testsuite/src/resources/test-configs/tomcat-webctx/deployers/jbossweb-tomcat6.sar/
trunk/testsuite/src/resources/test-configs/webservice-ssl/deployers/jbossweb-tomcat6.sar/
Log:
Update jbossweb-tomcat6.sar to jbossweb.deployer
Copied: trunk/testsuite/src/resources/test-configs/jacc/deployers/jbossweb.deployer (from rev 61395, trunk/testsuite/src/resources/test-configs/jacc/deployers/jbossweb-tomcat6.sar)
Copied: trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb.deployer (from rev 61395, trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb-tomcat6.sar)
Deleted: trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb.deployer/META-INF/jboss-service.xml
===================================================================
--- trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb-tomcat6.sar/META-INF/jboss-service.xml 2007-03-17 17:01:05 UTC (rev 61395)
+++ trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb.deployer/META-INF/jboss-service.xml 2007-03-17 17:26:46 UTC (rev 61398)
@@ -1,173 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Id$ -->
-
-<server>
-
- <!-- Tomcat 6 Service-->
- <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.jboss.web.tomcat.security.authenticators.JASPIFormAuthenticator</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 prefixes 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. The format
- is a comma separated list of the package names. There cannot be any
- whitespace between the package prefixes.
- This setting only applies when UseJBossWebLoader=false.
- -->
- <attribute name="FilteredPackages">javax.servlet,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>
-
- <!-- 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>
-
Copied: trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb.deployer/META-INF/war-deployers-beans.xml (from rev 61395, trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb-tomcat6.sar/META-INF/jboss-service.xml)
===================================================================
--- trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb.deployer/META-INF/war-deployers-beans.xml (rev 0)
+++ trunk/testsuite/src/resources/test-configs/jaspi/deployers/jbossweb.deployer/META-INF/war-deployers-beans.xml 2007-03-17 17:26:46 UTC (rev 61398)
@@ -0,0 +1,238 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!--
+ Web application deployers
+ $Id$
+-->
+<deployment xmlns="urn:jboss:bean-deployer:2.0">
+
+ <!-- Tomcat
+ <bean name="VFSClassLoader" class="org.jboss.virtual.classloading.VFSClassLoader">
+ <constructor factoryClass="org.jboss.virtual.classloading.VFSClassLoaderFactory"
+ factoryMethod="newClassLoader">
+ <parameter class="java.net.URI">${jboss.server.home.url}/deployers/jboss-web.deployer/</parameter>
+ <parameter>
+ <array class="[Ljava.lang.String;" elementClass="java.lang.String">
+ <value>*.jar</value>
+ <value>jsf-libs/*.jar</value>
+ </array>
+ </parameter>
+ </constructor>
+ </bean>
+ -->
+
+ <!-- web.xml parsing deployer -->
+ <bean name="WebAppParsingDeployer" class="org.jboss.deployment.WebAppParsingDeployer">
+ <install bean="MainDeployer" method="addDeployer">
+ <parameter><this/></parameter>
+ </install>
+ <uninstall bean="MainDeployer" method="removeDeployer">
+ <parameter><this/></parameter>
+ </uninstall>
+ <property name="type">war</property>
+ <property name="relativeOrder">2000</property>
+ </bean>
+ <bean name="JBossWebAppParsingDeployer" class="org.jboss.deployment.JBossWebAppParsingDeployer">
+ <install bean="MainDeployer" method="addDeployer">
+ <parameter><this/></parameter>
+ </install>
+ <uninstall bean="MainDeployer" method="removeDeployer">
+ <parameter><this/></parameter>
+ </uninstall>
+ <property name="type">war</property>
+ <property name="relativeOrder">2001</property>
+ </bean>
+
+ <!-- Allow for war local class loaders: in testing
+ <bean name="WarClassLoaderDeployer" class="org.jboss.web.tomcat.service.deployers.WarClassLoaderDeployer">
+ <install bean="MainDeployer" method="addDeployer">
+ <parameter><this/></parameter>
+ </install>
+ <uninstall bean="MainDeployer" method="removeDeployer">
+ <parameter><this/></parameter>
+ </uninstall>
+ <!- - CLASSLOADER_DEPLOYER - 1 - ->
+ <property name="relativeOrder">3999</property>
+ <!- - 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.
+ - ->
+ <property name="useJBossWebLoader">false</property>
+ <!- - The list of package prefixes 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. The format
+ is a comma separated list of the package names. There cannot be any
+ whitespace between the package prefixes.
+ This setting only applies when UseJBossWebLoader=false.
+ - ->
+ <property name="filteredPackages">javax.servlet,org.apache.commons.logging</property>
+ </bean>
+ -->
+
+ <!-- The WebMetaData to service mbean deployer -->
+ <bean name="WarDeployer" class="org.jboss.web.tomcat.service.deployers.TomcatDeployer">
+ <install bean="MainDeployer" method="addDeployer">
+ <parameter><this/></parameter>
+ </install>
+ <uninstall bean="MainDeployer" method="removeDeployer">
+ <parameter><this/></parameter>
+ </uninstall>
+
+ <property name="type">war</property>
+ <!-- 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
+ -->
+ <property name="authenticators">
+ <map class="java.util.Properties" keyClass="java.lang.String" valueClass="java.lang.String">
+ <entry>
+ <key>BASIC</key>
+ <value>org.apache.catalina.authenticator.BasicAuthenticator</value>
+ </entry>
+ <entry>
+ <key>CLIENT-CERT</key>
+ <value>org.apache.catalina.authenticator.SSLAuthenticator</value>
+ </entry>
+ <entry>
+ <key>DIGEST</key>
+ <value>org.apache.catalina.authenticator.DigestAuthenticator</value>
+ </entry>
+ <entry>
+ <key>FORM</key>
+ <value>org.jboss.web.tomcat.security.authenticators.JASPIFormAuthenticator</value>
+ </entry>
+ <entry>
+ <key>NONE</key>
+ <value>org.apache.catalina.authenticator.NonLoginAuthenticator</value>
+ </entry>
+ </map>
+ </property>
+
+ <!-- The JAAS security domain to use in the absense of an explicit
+ security-domain specification in the war WEB-INF/jboss-web.xml
+ -->
+ <property name="defaultSecurityDomain">java:/jaas/other</property>
+
+ <!-- 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.
+ -->
+ <property name="java2ClassLoadingCompliance">false</property>
+ <!-- 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.
+ -->
+ <property name="useJBossWebLoader">false</property>
+ <!-- The list of package prefixes 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. The format
+ is a comma separated list of the package names. There cannot be any
+ whitespace between the package prefixes.
+ This setting only applies when UseJBossWebLoader=false.
+ -->
+ <property name="filteredPackages">javax.servlet,org.apache.commons.logging</property>
+
+ <property name="lenientEjbLink">true</property>
+
+ <!--Flag to delete the Work Dir on Context Destroy -->
+ <property name="deleteWorkDirOnContextDestroy">false</property>
+
+ <!--
+ Class of the session manager (used if context is marked as 'distributable'. Currently allowed values:
+ - org.jboss.web.tomcat.service.session.JBossCacheManager
+ -->
+ <property name="managerClass">org.jboss.web.tomcat.service.session.JBossCacheManager</property>
+
+ <!-- The class used as the deployment wrapper -->
+ <property name="deploymentClass">org.jboss.web.tomcat.service.deployers.TomcatDeployment</property>
+
+ <!-- The name of the request property under with the authenticated JAAS
+ Subject is stored on successful authentication. If null or empty then
+ the Subject will not be stored.
+ -->
+ <!--
+ <property name="subjectAttributeName">j_subject</property>
+ -->
+
+ <!-- The SessionIdAlphabet is the set of characters used to create a session Id
+ It must be made up of exactly 65 unique characters
+ <property name="sessionIdAlphabet">ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+-*</property>
+ -->
+
+ <!--
+ *******************************************************
+ ****************** 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 propertys 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 propertys
+ 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" property is not used.
+ The "interval" mode, in association with the "SnapshotInterval"
+ property, indicates that modified sessions will only be replicated
+ every "SnapshotInterval" milliseconds at most.
+
+ Note that this property 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.)
+ -->
+ <property name="snapshotMode">instant</property> <!-- you may switch to "interval" -->
+ <property name="snapshotInterval">2000</property>
+
+ <!--
+ 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.
+ -->
+ <property name="useJK">false</property>
+
+ <property name="domain">jboss.web</property>
+ <property name="securityManagerService">
+ <inject bean="jboss.security:service=JaasSecurityManager" />
+ </property>
+
+ <depends>jboss:service=TransactionManager</depends>
+ <depends>SecurityDeployer</depends>
+
+ <!-- Only needed if the org.jboss.web.tomcat.service.jca.CachedConnectionValve
+ TODO: injection
+ is enabled in the tomcat server.xml file.
+ <depends>jboss.jca:service=CachedConnectionManager</depends>
+ -->
+ </bean>
+
+</deployment>
Copied: trunk/testsuite/src/resources/test-configs/tomcat-ssl/deployers/jbossweb.deployer (from rev 61395, trunk/testsuite/src/resources/test-configs/tomcat-ssl/deployers/jbossweb-tomcat6.sar)
Deleted: trunk/testsuite/src/resources/test-configs/tomcat-ssl/deployers/jbossweb.deployer/META-INF/jboss-service.xml
===================================================================
--- trunk/testsuite/src/resources/test-configs/tomcat-ssl/deployers/jbossweb-tomcat6.sar/META-INF/jboss-service.xml 2007-03-17 17:01:05 UTC (rev 61395)
+++ trunk/testsuite/src/resources/test-configs/tomcat-ssl/deployers/jbossweb.deployer/META-INF/jboss-service.xml 2007-03-17 17:26:46 UTC (rev 61398)
@@ -1,84 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<server>
-
- <mbean code="org.jboss.web.tomcat.tc6.Tomcat6"
- name="jboss.web:service=WebServer" xmbean-dd="META-INF/webserver-xmbean.xml">
-
- <!-- 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">true</attribute>
-
- <attribute name="LenientEjbLink">true</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.
- -->
- <attribute name="UseJBossWebLoader">true</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>
- -->
- <!-- A flag indicating whether web-apps may set themselfs as privileged
- in their custom WEB-INF/context.xml context configuration.
- -->
- <attribute name="AllowSelfPrivilegedWebApps">false</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>
-
- <attribute name="Domain">jboss.web</attribute>
- <depends>jboss.security:service=SecurityDomain</depends>
- <depends>jboss.security:service=PBESecurityDomain</depends>
- </mbean>
-
-</server>
-
Added: trunk/testsuite/src/resources/test-configs/tomcat-webctx/deployers/jbossweb.deployer/META-INF/war-deployer-beans.xml
===================================================================
--- trunk/testsuite/src/resources/test-configs/tomcat-webctx/deployers/jbossweb.deployer/META-INF/war-deployer-beans.xml (rev 0)
+++ trunk/testsuite/src/resources/test-configs/tomcat-webctx/deployers/jbossweb.deployer/META-INF/war-deployer-beans.xml 2007-03-17 17:26:46 UTC (rev 61398)
@@ -0,0 +1,238 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!--
+ Web application deployers
+ $Id:$
+-->
+<deployment xmlns="urn:jboss:bean-deployer:2.0">
+
+ <!-- Tomcat
+ <bean name="VFSClassLoader" class="org.jboss.virtual.classloading.VFSClassLoader">
+ <constructor factoryClass="org.jboss.virtual.classloading.VFSClassLoaderFactory"
+ factoryMethod="newClassLoader">
+ <parameter class="java.net.URI">${jboss.server.home.url}/deployers/jboss-web.deployer/</parameter>
+ <parameter>
+ <array class="[Ljava.lang.String;" elementClass="java.lang.String">
+ <value>*.jar</value>
+ <value>jsf-libs/*.jar</value>
+ </array>
+ </parameter>
+ </constructor>
+ </bean>
+ -->
+
+ <!-- web.xml parsing deployer -->
+ <bean name="WebAppParsingDeployer" class="org.jboss.deployment.WebAppParsingDeployer">
+ <install bean="MainDeployer" method="addDeployer">
+ <parameter><this/></parameter>
+ </install>
+ <uninstall bean="MainDeployer" method="removeDeployer">
+ <parameter><this/></parameter>
+ </uninstall>
+ <property name="type">war</property>
+ <property name="relativeOrder">2000</property>
+ </bean>
+ <bean name="JBossWebAppParsingDeployer" class="org.jboss.deployment.JBossWebAppParsingDeployer">
+ <install bean="MainDeployer" method="addDeployer">
+ <parameter><this/></parameter>
+ </install>
+ <uninstall bean="MainDeployer" method="removeDeployer">
+ <parameter><this/></parameter>
+ </uninstall>
+ <property name="type">war</property>
+ <property name="relativeOrder">2001</property>
+ </bean>
+
+ <!-- Allow for war local class loaders: in testing
+ <bean name="WarClassLoaderDeployer" class="org.jboss.web.tomcat.service.deployers.WarClassLoaderDeployer">
+ <install bean="MainDeployer" method="addDeployer">
+ <parameter><this/></parameter>
+ </install>
+ <uninstall bean="MainDeployer" method="removeDeployer">
+ <parameter><this/></parameter>
+ </uninstall>
+ <!- - CLASSLOADER_DEPLOYER - 1 - ->
+ <property name="relativeOrder">3999</property>
+ <!- - 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.
+ - ->
+ <property name="useJBossWebLoader">false</property>
+ <!- - The list of package prefixes 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. The format
+ is a comma separated list of the package names. There cannot be any
+ whitespace between the package prefixes.
+ This setting only applies when UseJBossWebLoader=false.
+ - ->
+ <property name="filteredPackages">javax.servlet,org.apache.commons.logging</property>
+ </bean>
+ -->
+
+ <!-- The WebMetaData to service mbean deployer -->
+ <bean name="WarDeployer" class="org.jboss.web.tomcat.service.deployers.TomcatDeployer">
+ <install bean="MainDeployer" method="addDeployer">
+ <parameter><this/></parameter>
+ </install>
+ <uninstall bean="MainDeployer" method="removeDeployer">
+ <parameter><this/></parameter>
+ </uninstall>
+
+ <property name="type">war</property>
+ <!-- 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
+ -->
+ <property name="authenticators">
+ <map class="java.util.Properties" keyClass="java.lang.String" valueClass="java.lang.String">
+ <entry>
+ <key>BASIC</key>
+ <value>org.apache.catalina.authenticator.BasicAuthenticator</value>
+ </entry>
+ <entry>
+ <key>CLIENT-CERT</key>
+ <value>org.apache.catalina.authenticator.SSLAuthenticator</value>
+ </entry>
+ <entry>
+ <key>DIGEST</key>
+ <value>org.apache.catalina.authenticator.DigestAuthenticator</value>
+ </entry>
+ <entry>
+ <key>FORM</key>
+ <value>org.apache.catalina.authenticator.FormAuthenticator</value>
+ </entry>
+ <entry>
+ <key>NONE</key>
+ <value>org.apache.catalina.authenticator.NonLoginAuthenticator</value>
+ </entry>
+ </map>
+ </property>
+
+ <!-- The JAAS security domain to use in the absense of an explicit
+ security-domain specification in the war WEB-INF/jboss-web.xml
+ -->
+ <property name="defaultSecurityDomain">java:/jaas/other</property>
+
+ <!-- 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.
+ -->
+ <property name="java2ClassLoadingCompliance">false</property>
+ <!-- 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.
+ -->
+ <property name="useJBossWebLoader">true</property>
+ <!-- The list of package prefixes 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. The format
+ is a comma separated list of the package names. There cannot be any
+ whitespace between the package prefixes.
+ This setting only applies when UseJBossWebLoader=false.
+ -->
+ <property name="filteredPackages">javax.servlet</property>
+
+ <property name="lenientEjbLink">true</property>
+
+ <!--Flag to delete the Work Dir on Context Destroy -->
+ <property name="deleteWorkDirOnContextDestroy">false</property>
+
+ <!--
+ Class of the session manager (used if context is marked as 'distributable'. Currently allowed values:
+ - org.jboss.web.tomcat.service.session.JBossCacheManager
+ -->
+ <property name="managerClass">org.jboss.web.tomcat.service.session.JBossCacheManager</property>
+
+ <!-- The class used as the deployment wrapper -->
+ <property name="deploymentClass">org.jboss.web.tomcat.service.deployers.TomcatDeployment</property>
+
+ <!-- The name of the request property under with the authenticated JAAS
+ Subject is stored on successful authentication. If null or empty then
+ the Subject will not be stored.
+ -->
+ <!--
+ <property name="subjectAttributeName">j_subject</property>
+ -->
+
+ <!-- The SessionIdAlphabet is the set of characters used to create a session Id
+ It must be made up of exactly 65 unique characters
+ <property name="sessionIdAlphabet">ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+-*</property>
+ -->
+
+ <!--
+ *******************************************************
+ ****************** 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 propertys 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 propertys
+ 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" property is not used.
+ The "interval" mode, in association with the "SnapshotInterval"
+ property, indicates that modified sessions will only be replicated
+ every "SnapshotInterval" milliseconds at most.
+
+ Note that this property 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.)
+ -->
+ <property name="snapshotMode">instant</property> <!-- you may switch to "interval" -->
+ <property name="snapshotInterval">2000</property>
+
+ <!--
+ 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.
+ -->
+ <property name="useJK">false</property>
+
+ <property name="domain">jboss.web</property>
+ <property name="securityManagerService">
+ <inject bean="jboss.security:service=JaasSecurityManager" />
+ </property>
+
+ <depends>jboss:service=TransactionManager</depends>
+ <depends>SecurityDeployer</depends>
+
+ <!-- Only needed if the org.jboss.web.tomcat.service.jca.CachedConnectionValve
+ TODO: injection
+ is enabled in the tomcat server.xml file.
+ <depends>jboss.jca:service=CachedConnectionManager</depends>
+ -->
+ </bean>
+
+</deployment>
Property changes on: trunk/testsuite/src/resources/test-configs/tomcat-webctx/deployers/jbossweb.deployer/META-INF/war-deployer-beans.xml
___________________________________________________________________
Name: svn:keywords
+ Id,Revision
Name: svn:eol-style
+ native
Copied: trunk/testsuite/src/resources/test-configs/webservice-ssl/deployers/jbossweb.deployer (from rev 61395, trunk/testsuite/src/resources/test-configs/webservice-ssl/deployers/jbossweb-tomcat6.sar)
More information about the jboss-cvs-commits
mailing list