[jboss-cvs] JBossAS SVN: r76357 - trunk/cluster/src/etc.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Jul 29 05:58:10 EDT 2008
Author: adrian at jboss.org
Date: 2008-07-29 05:58:10 -0400 (Tue, 29 Jul 2008)
New Revision: 76357
Added:
trunk/cluster/src/etc/deploy-hasingleton-jboss-beans.xml
Removed:
trunk/cluster/src/etc/deploy-hasingleton-beans.xml
Log:
[JBAS-5803] beans.xml -> jboss-beans.xml
Deleted: trunk/cluster/src/etc/deploy-hasingleton-beans.xml
===================================================================
--- trunk/cluster/src/etc/deploy-hasingleton-beans.xml 2008-07-29 09:57:43 UTC (rev 76356)
+++ trunk/cluster/src/etc/deploy-hasingleton-beans.xml 2008-07-29 09:58:10 UTC (rev 76357)
@@ -1,131 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<deployment xmlns="urn:jboss:bean-deployer:2.0">
-
-<!-- ===================================================================== -->
-<!-- -->
-<!-- This service ensures that exactly one node in the cluster -->
-<!-- deploys the services under "deploy-hasingleton" -->
-<!-- -->
-<!-- ===================================================================== -->
-
- <!--
- |
- | Deployment scanner that can be called by an HASingletonController
- |
- -->
- <bean name="HASingletonDeploymentScanner" class="org.jboss.ha.singleton.HASingletonDeploymentScanner">
-
- <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=HASingletonDeploymentScanner,partition=${jboss.partition.name:DefaultPartition}", exposedInterface=org.jboss.ha.singleton.HASingletonDeploymentScannerMBean.class, registerDirectly=true)</annotation>
-
- <property name="profileService"><inject bean="ProfileService"/></property>
- <property name="filterInstance"><inject bean="DeploymentFilter"/></property>
- <property name="mainDeployer"><inject bean="MainDeployer"/></property>
- </bean>
-
- <!--
- |
- | Use the deployer service on the singleton node.
- |
- -->
- <bean name="HASingletonDeployer"
- class="org.jboss.ha.singleton.HASingletonController">
-
- <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.ha:service=HASingletonDeployer", exposedInterface=org.jboss.ha.singleton.HASingletonControllerMBean.class, registerDirectly=true)</annotation>
-
- <depends>HAPartition</depends>
-
- <property name="HAPartition"><inject bean="HAPartition"/></property>
- <property name="target"><inject bean="HASingletonDeploymentScanner"/></property>
- <property name="targetStartMethod">deploySingletons</property>
- <property name="targetStartMethodArgument">${jboss.server.home.url}deploy-hasingleton</property>
- <property name="targetStopMethod">undeploySingletons</property>
- <property name="targetStopMethodArgument">${jboss.server.home.url}deploy-hasingleton</property>
-
- <!-- whether to register thread context classloader for the RPC handler, default is false -->
- <!--<property name="registerThreadContextClassLoader">false</property>-->
-
- <!-- Whether the singleton should be restarted (i.e. invoke the TargetStopMethod and then the
- TargetStartMethod) if a cluster merge occurs while this node is the singleton master.
- A cluster merge means there may have been more than one singleton master during the period
- when communication between some or all of the nodes in the cluster was disrupted; hence the
- surviving master may not be aware of state changes made by another master. Restarting the
- singleton gives it a signal that it should refresh its internal state from any external
- store.
- By default this is set to true.
- -->
- <property name="restartOnMerge">true</property>
-
- </bean>
-
- <!--
- | A BarrierController that controls the lifecycle of a Barrier mbean
- | based on notifications received by the HASingletonController above.
- |
- | Services deployed normally inside ./deploy or ./farm that want to be
- | started/stopped whenever the content of ./deploy-hasingleton/ gets
- | deployed/undeployed, or else, whenever the current node becomes the
- | master, need only specify a dependency on the Barrier:
- |
- | <depends>jboss.ha:service=HASingletonDeployer,type=Barrier</depends>
- |
- | With this setup the Barrier and all services that depend on it
- | will be started *after* the content of deploy-hasingleton is deployed.
- | To change this, just use the following enabled notification types:
- |
- | <enable type="org.jboss.ha.singleton.starting"/>
- | <enable type="org.jboss.ha.singleton.stopped"/>
- -->
- <bean class="org.jboss.system.BarrierController"
- name="jboss.ha:service=HASingletonDeployer,type=BarrierController">
-
- <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.ha:service=HASingletonDeployer,type=BarrierControllerMBean", exposedInterface=org.jboss.system.BarrierControllerMBean.class, registerDirectly=true)</annotation>
-
- <!-- Dependent services will depend on this mbean -->
- <property name="barrierObjectName">jboss.ha:service=HASingletonDeployer,type=Barrier</property>
-
- <!-- Whether to subscribe for notifications after startup -->
- <property name="dynamicSubscriptions">false</property>
- <!-- The notification subscription handback that starts the barrier -->
- <property name="startBarrierHandback">start</property>
- <!-- The notification subscription handback that stops the barrier -->
- <property name="stopBarrierHandback">stop</property>
-
- <!-- The notifications to subscribe for, along with their handbacks -->
- <property name="subscriptions">
- <list>
- <!--value-->
- <bean name="HASingletonDeployerStartSubscription" class="org.jboss.system.ListenerServiceMBeanSupport$SubscriptionInfo">
- <constructor>
- <parameter>jboss.ha:service=HASingletonDeployer</parameter>
- <parameter>start</parameter>
- <parameter>
- <bean name="HASingletonDeployerStartSubscriptionNotificationFilter" class="javax.management.NotificationFilterSupport">
- <install method="enableType">
- <parameter>org.jboss.ha.singleton.started</parameter>
- </install>
- </bean>
- </parameter>
- </constructor>
- </bean>
- <!--/value>
- <value-->
- <bean name="HASingletonDeployerStopSubscription" class="org.jboss.system.ListenerServiceMBeanSupport$SubscriptionInfo">
- <constructor>
- <parameter>jboss.ha:service=HASingletonDeployer</parameter>
- <parameter>stop</parameter>
- <parameter>
- <bean name="HASingletonDeployerStopSubscriptionNotificationFilter" class="javax.management.NotificationFilterSupport">
- <install method="enableType">
- <parameter>org.jboss.ha.singleton.stopping</parameter>
- </install>
- </bean>
- </parameter>
- </constructor>
- </bean>
- <!--/value-->
- </list>
- </property>
- </bean>
-
-</deployment>
Copied: trunk/cluster/src/etc/deploy-hasingleton-jboss-beans.xml (from rev 76356, trunk/cluster/src/etc/deploy-hasingleton-beans.xml)
===================================================================
--- trunk/cluster/src/etc/deploy-hasingleton-jboss-beans.xml (rev 0)
+++ trunk/cluster/src/etc/deploy-hasingleton-jboss-beans.xml 2008-07-29 09:58:10 UTC (rev 76357)
@@ -0,0 +1,131 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<deployment xmlns="urn:jboss:bean-deployer:2.0">
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- This service ensures that exactly one node in the cluster -->
+<!-- deploys the services under "deploy-hasingleton" -->
+<!-- -->
+<!-- ===================================================================== -->
+
+ <!--
+ |
+ | Deployment scanner that can be called by an HASingletonController
+ |
+ -->
+ <bean name="HASingletonDeploymentScanner" class="org.jboss.ha.singleton.HASingletonDeploymentScanner">
+
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=HASingletonDeploymentScanner,partition=${jboss.partition.name:DefaultPartition}", exposedInterface=org.jboss.ha.singleton.HASingletonDeploymentScannerMBean.class, registerDirectly=true)</annotation>
+
+ <property name="profileService"><inject bean="ProfileService"/></property>
+ <property name="filterInstance"><inject bean="DeploymentFilter"/></property>
+ <property name="mainDeployer"><inject bean="MainDeployer"/></property>
+ </bean>
+
+ <!--
+ |
+ | Use the deployer service on the singleton node.
+ |
+ -->
+ <bean name="HASingletonDeployer"
+ class="org.jboss.ha.singleton.HASingletonController">
+
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.ha:service=HASingletonDeployer", exposedInterface=org.jboss.ha.singleton.HASingletonControllerMBean.class, registerDirectly=true)</annotation>
+
+ <depends>HAPartition</depends>
+
+ <property name="HAPartition"><inject bean="HAPartition"/></property>
+ <property name="target"><inject bean="HASingletonDeploymentScanner"/></property>
+ <property name="targetStartMethod">deploySingletons</property>
+ <property name="targetStartMethodArgument">${jboss.server.home.url}deploy-hasingleton</property>
+ <property name="targetStopMethod">undeploySingletons</property>
+ <property name="targetStopMethodArgument">${jboss.server.home.url}deploy-hasingleton</property>
+
+ <!-- whether to register thread context classloader for the RPC handler, default is false -->
+ <!--<property name="registerThreadContextClassLoader">false</property>-->
+
+ <!-- Whether the singleton should be restarted (i.e. invoke the TargetStopMethod and then the
+ TargetStartMethod) if a cluster merge occurs while this node is the singleton master.
+ A cluster merge means there may have been more than one singleton master during the period
+ when communication between some or all of the nodes in the cluster was disrupted; hence the
+ surviving master may not be aware of state changes made by another master. Restarting the
+ singleton gives it a signal that it should refresh its internal state from any external
+ store.
+ By default this is set to true.
+ -->
+ <property name="restartOnMerge">true</property>
+
+ </bean>
+
+ <!--
+ | A BarrierController that controls the lifecycle of a Barrier mbean
+ | based on notifications received by the HASingletonController above.
+ |
+ | Services deployed normally inside ./deploy or ./farm that want to be
+ | started/stopped whenever the content of ./deploy-hasingleton/ gets
+ | deployed/undeployed, or else, whenever the current node becomes the
+ | master, need only specify a dependency on the Barrier:
+ |
+ | <depends>jboss.ha:service=HASingletonDeployer,type=Barrier</depends>
+ |
+ | With this setup the Barrier and all services that depend on it
+ | will be started *after* the content of deploy-hasingleton is deployed.
+ | To change this, just use the following enabled notification types:
+ |
+ | <enable type="org.jboss.ha.singleton.starting"/>
+ | <enable type="org.jboss.ha.singleton.stopped"/>
+ -->
+ <bean class="org.jboss.system.BarrierController"
+ name="jboss.ha:service=HASingletonDeployer,type=BarrierController">
+
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.ha:service=HASingletonDeployer,type=BarrierControllerMBean", exposedInterface=org.jboss.system.BarrierControllerMBean.class, registerDirectly=true)</annotation>
+
+ <!-- Dependent services will depend on this mbean -->
+ <property name="barrierObjectName">jboss.ha:service=HASingletonDeployer,type=Barrier</property>
+
+ <!-- Whether to subscribe for notifications after startup -->
+ <property name="dynamicSubscriptions">false</property>
+ <!-- The notification subscription handback that starts the barrier -->
+ <property name="startBarrierHandback">start</property>
+ <!-- The notification subscription handback that stops the barrier -->
+ <property name="stopBarrierHandback">stop</property>
+
+ <!-- The notifications to subscribe for, along with their handbacks -->
+ <property name="subscriptions">
+ <list>
+ <!--value-->
+ <bean name="HASingletonDeployerStartSubscription" class="org.jboss.system.ListenerServiceMBeanSupport$SubscriptionInfo">
+ <constructor>
+ <parameter>jboss.ha:service=HASingletonDeployer</parameter>
+ <parameter>start</parameter>
+ <parameter>
+ <bean name="HASingletonDeployerStartSubscriptionNotificationFilter" class="javax.management.NotificationFilterSupport">
+ <install method="enableType">
+ <parameter>org.jboss.ha.singleton.started</parameter>
+ </install>
+ </bean>
+ </parameter>
+ </constructor>
+ </bean>
+ <!--/value>
+ <value-->
+ <bean name="HASingletonDeployerStopSubscription" class="org.jboss.system.ListenerServiceMBeanSupport$SubscriptionInfo">
+ <constructor>
+ <parameter>jboss.ha:service=HASingletonDeployer</parameter>
+ <parameter>stop</parameter>
+ <parameter>
+ <bean name="HASingletonDeployerStopSubscriptionNotificationFilter" class="javax.management.NotificationFilterSupport">
+ <install method="enableType">
+ <parameter>org.jboss.ha.singleton.stopping</parameter>
+ </install>
+ </bean>
+ </parameter>
+ </constructor>
+ </bean>
+ <!--/value-->
+ </list>
+ </property>
+ </bean>
+
+</deployment>
More information about the jboss-cvs-commits
mailing list