[jboss-cvs] JBossAS SVN: r73819 - trunk/testsuite/src/resources/web/federation/authext.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu May 29 17:21:23 EDT 2008
Author: dimitris at jboss.org
Date: 2008-05-29 17:21:22 -0400 (Thu, 29 May 2008)
New Revision: 73819
Modified:
trunk/testsuite/src/resources/web/federation/authext/war-deployers-beans.xml
Log:
fix this bloody config
Modified: trunk/testsuite/src/resources/web/federation/authext/war-deployers-beans.xml
===================================================================
--- trunk/testsuite/src/resources/web/federation/authext/war-deployers-beans.xml 2008-05-29 18:39:12 UTC (rev 73818)
+++ trunk/testsuite/src/resources/web/federation/authext/war-deployers-beans.xml 2008-05-29 21:21:22 UTC (rev 73819)
@@ -14,91 +14,91 @@
<bean name="JBossWebAppParsingDeployer" class="org.jboss.deployment.JBossWebAppParsingDeployer">
<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">
- <property name="relativeOrder">-1</property>
-
- <property name="includeWebInfInClasspath">true</property>
- <property name="filteredPackages">javax.servlet,org.apache.commons.logging</property>
-
- </bean>
-
- <!--
- Injects default clustering metadata.
- TODO. A better approach is to use a jboss-web.xml equivalent to conf/web.xml
- and conf/standardjboss.xml as the source for defaults.
- -->
- <bean name="WebAppClusteringDefaultsDeployer"
- class="org.jboss.web.tomcat.service.deployers.ClusteringDefaultsDeployer">
-
- <property name="relativeOrder">2002</property>
-
- <!--<property name="cacheSource">jboss.cache:service=TomcatClusteringCache</property>-->
-
- <property name="cacheName">jboss.cache:service=TomcatClusteringCache</property>
-
- <!--
- The following two properties define when sessions are replicated to
- the other nodes.
- The default value, "instant", uses the request thread to replicate changes
- to the other nodes at the end of requests. In this case, the
- "SnapshotInterval" property is not used.
- The "interval" mode uses a background thread that periodically checks for
- modified sessions and replicates them. The "SnapshotInterval"
- property controls how often (in milliseconds) the background thread
- should run.
-
- 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>
- <property name="snapshotInterval">1000</property>
-
- <property name="replicationGranularity">SESSION</property>
- <property name="replicationTrigger">SET_AND_NON_PRIMITIVE_GET</property>
- <property name="replicationFieldBatchMode">true</property>
-
- <!--
- Whether by default to add special session handling to coordinate use
- with mod_jk or other JK connector variants.
- If a JK connector is used, you will need to set the JvmRoute inside
- JBossWeb, e.g. configure,
- Engine name="jboss.web" jvmRoute="Node1" defaultHost="localhost"
- in server.xml.
-
- This value can be configured per webapp in the webapp's jboss.xml.
-
- If not set, the default will be to add the special session handling
- if a jvmRoute is configured on the Engine. So, generally the only reason
- to configure this overall default is to set it to 'false' and thus force
- per webapp configuration.
- -->
- <!--
- <property name="useJK">false</property>
- -->
-
- <property name="useSessionPassivation">false</property>
- <property name="passivationMaxIdleTime">-1</property>
- <property name="passivationMinIdleTime">-1</property>
-
- </bean>
-
- <!--
- Adds to distributable webapps dependencies on any needed clustering services.
-
- With this deployer in place, webapps marked <distributable/> will not
- deploy completely in the absence of needed clustering support services.
-
- If desired, this deployer can be commented out in a non-clustered AS
- configuration (e.g. 'default') in which case a <distributable/> webapp
- will still deploy after logging a WARN about the missing clustering
- services. The webapp's sessions will not be clustered. This was the
- behavior of distributable webapps in the 'default' config in AS 4.x.
- -->
- <bean name="WebAppClusteringDependencyDeployer"
+ </bean>
+
+ <!-- Allow for war local class loaders: in testing -->
+ <bean name="WarClassLoaderDeployer" class="org.jboss.web.tomcat.service.deployers.WarClassLoaderDeployer">
+ <property name="relativeOrder">-1</property>
+
+ <property name="includeWebInfInClasspath">true</property>
+ <property name="filteredPackages">javax.servlet,org.apache.commons.logging</property>
+
+ </bean>
+
+ <!--
+ Injects default clustering metadata.
+ TODO. A better approach is to use a jboss-web.xml equivalent to conf/web.xml
+ and conf/standardjboss.xml as the source for defaults.
+ -->
+ <bean name="WebAppClusteringDefaultsDeployer"
+ class="org.jboss.web.tomcat.service.deployers.ClusteringDefaultsDeployer">
+
+ <property name="relativeOrder">2002</property>
+
+ <!--<property name="cacheSource">jboss.cache:service=TomcatClusteringCache</property>-->
+
+ <property name="cacheName">jboss.cache:service=TomcatClusteringCache</property>
+
+ <!--
+ The following two properties define when sessions are replicated to
+ the other nodes.
+ The default value, "instant", uses the request thread to replicate changes
+ to the other nodes at the end of requests. In this case, the
+ "SnapshotInterval" property is not used.
+ The "interval" mode uses a background thread that periodically checks for
+ modified sessions and replicates them. The "SnapshotInterval"
+ property controls how often (in milliseconds) the background thread
+ should run.
+
+ 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>
+ <property name="snapshotInterval">1000</property>
+
+ <property name="replicationGranularity">SESSION</property>
+ <property name="replicationTrigger">SET_AND_NON_PRIMITIVE_GET</property>
+ <property name="replicationFieldBatchMode">true</property>
+
+ <!--
+ Whether by default to add special session handling to coordinate use
+ with mod_jk or other JK connector variants.
+ If a JK connector is used, you will need to set the JvmRoute inside
+ JBossWeb, e.g. configure,
+ Engine name="jboss.web" jvmRoute="Node1" defaultHost="localhost"
+ in server.xml.
+
+ This value can be configured per webapp in the webapp's jboss.xml.
+
+ If not set, the default will be to add the special session handling
+ if a jvmRoute is configured on the Engine. So, generally the only reason
+ to configure this overall default is to set it to 'false' and thus force
+ per webapp configuration.
+ -->
+ <!--
+ <property name="useJK">false</property>
+ -->
+
+ <property name="useSessionPassivation">false</property>
+ <property name="passivationMaxIdleTime">-1</property>
+ <property name="passivationMinIdleTime">-1</property>
+
+ </bean>
+
+ <!--
+ Adds to distributable webapps dependencies on any needed clustering services.
+
+ With this deployer in place, webapps marked <distributable/> will not
+ deploy completely in the absence of needed clustering support services.
+
+ If desired, this deployer can be commented out in a non-clustered AS
+ configuration (e.g. 'default') in which case a <distributable/> webapp
+ will still deploy after logging a WARN about the missing clustering
+ services. The webapp's sessions will not be clustered. This was the
+ behavior of distributable webapps in the 'default' config in AS 4.x.
+ -->
+ <bean name="WebAppClusteringDependencyDeployer"
class="org.jboss.web.tomcat.service.deployers.ClusteringDependencyDeployer"/>
<bean name="WarDeployer" class="org.jboss.web.tomcat.service.deployers.TomcatDeployer">
@@ -132,11 +132,11 @@
<entry>
<key>NONE</key>
<value>org.apache.catalina.authenticator.NonLoginAuthenticator</value>
- </entry>
- <entry>
- <key>HEADER</key>
- <value>org.jboss.test.web.security.authenticators.HeaderAuthenticator</value>
</entry>
+ <entry>
+ <key>HEADER</key>
+ <value>org.jboss.test.web.security.authenticators.HeaderAuthenticator</value>
+ </entry>
</map>
</property>
@@ -196,6 +196,8 @@
<inject bean="jboss.security:service=JaasSecurityManager" />
</property>
+ <!-- Specify PolicyRegistration-->
+ <property name="policyRegistrationName">JBossSecurityPolicyRegistration</property>
<!-- Specify a SecurityManagement Wrapper -->
<property name="securityManagementName">JNDIBasedSecurityManagement</property>
More information about the jboss-cvs-commits
mailing list