[jboss-cvs] JBossAS SVN: r94125 - projects/docs/community/5/Clustering_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Sep 29 17:55:31 EDT 2009
Author: bstansberry at jboss.com
Date: 2009-09-29 17:55:31 -0400 (Tue, 29 Sep 2009)
New Revision: 94125
Modified:
projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_Building_Blocks.xml
Log:
Properly size graphic, prevent config example page width overflow
Modified: projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_Building_Blocks.xml
===================================================================
--- projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_Building_Blocks.xml 2009-09-29 21:42:16 UTC (rev 94124)
+++ projects/docs/community/5/Clustering_Guide/en-US/Clustering_Guide_Building_Blocks.xml 2009-09-29 21:55:31 UTC (rev 94125)
@@ -240,7 +240,7 @@
<title>Services using a Shared Transport</title>
<mediaobject>
<imageobject>
- <imagedata align="center" fileref="images/clustering-SharedTransport.png" />
+ <imagedata align="center" scalefit="1" fileref="images/clustering-SharedTransport.png" />
</imageobject>
</mediaobject>
</figure>
@@ -533,47 +533,43 @@
<para>The following snippet shows the <literal>HAPartition</literal> service definition packaged with the standard JBoss AS distribution.
This configuration can be found in the <literal>server/all/deploy/cluster/hapartition-jboss-beans.xml</literal> file.
</para>
- <programlisting><![CDATA[
- <bean name="HAPartitionCacheHandler"
- class="org.jboss.ha.framework.server.HAPartitionCacheHandlerImpl">
- <property name="cacheManager"><inject bean="CacheManager"/></property>
- <property name="cacheConfigName">ha-partition</property>
- </bean>
+ <programlisting><![CDATA[<bean name="HAPartitionCacheHandler"
+ class="org.jboss.ha.framework.server.HAPartitionCacheHandlerImpl">
+ <property name="cacheManager"><inject bean="CacheManager"/></property>
+ <property name="cacheConfigName">ha-partition</property>
+</bean>
- <bean name="HAPartition"
- class="org.jboss.ha.framework.server.ClusterPartition">
+<bean name="HAPartition" class="org.jboss.ha.framework.server.ClusterPartition">
- <depends>jboss:service=Naming</depends>
-
- <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=HAPartition,partition=${jboss.partition.name:DefaultPartition}", exposedInterface=org.jboss.ha.framework.server.ClusterPartitionMBean.class, registerDirectly=true)</annotation>
+ <depends>jboss:service=Naming</depends>
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(...)</annotation>
- <!-- ClusterPartition requires a Cache for state management -->
- <property name="cacheHandler"><inject bean="HAPartitionCacheHandler"/></property>
-
- <!-- Name of the partition being built -->
- <property name="partitionName">${jboss.partition.name:DefaultPartition}</property>
-
- <!-- The address used to determine the node name -->
- <property name="nodeAddress">${jboss.bind.address}</property>
-
- <!-- Max time (in ms) to wait for state transfer to complete. Increase for large states -->
- <property name="stateTransferTimeout">30000</property>
-
- <!-- Max time (in ms) to wait for RPC calls to complete. -->
- <property name="methodCallTimeout">60000</property>
+ <!-- ClusterPartition requires a Cache for state management -->
+ <property name="cacheHandler"><inject bean="HAPartitionCacheHandler"/></property>
+ <!-- Name of the partition being built -->
+ <property name="partitionName">${jboss.partition.name:DefaultPartition}</property>
+ <!-- The address used to determine the node name -->
+ <property name="nodeAddress">${jboss.bind.address}</property>
+ <!-- Max time (in ms) to wait for state transfer to complete. -->
+ <property name="stateTransferTimeout">30000</property>
+ <!-- Max time (in ms) to wait for RPC calls to complete. -->
+ <property name="methodCallTimeout">60000</property>
+
+ <!-- Optionally provide a thread source to allow async connect of our channel -->
+ <property name="threadPool">
+ <inject bean="jboss.system:service=ThreadPool"/>
+ </property>
- <!-- Optionally provide a thread source to allow async connect of our channel -->
- <property name="threadPool"><inject bean="jboss.system:service=ThreadPool"/></property>
-
- <property name="distributedStateImpl">
- <bean name="DistributedState"
- class="org.jboss.ha.framework.server.DistributedStateImpl">
- <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=DistributedState,partitionName=${jboss.partition.name:DefaultPartition}", exposedInterface=org.jboss.ha.framework.server.DistributedStateImplMBean.class, registerDirectly=true)</annotation>
- <property name="cacheHandler"><inject bean="HAPartitionCacheHandler"/></property>
- </bean>
- </property>
-
- </bean>]]></programlisting>
+ <property name="distributedStateImpl">
+ <bean name="DistributedState"
+ class="org.jboss.ha.framework.server.DistributedStateImpl">
+ <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(...)</annotation>
+ <property name="cacheHandler">
+ <inject bean="HAPartitionCacheHandler"/>
+ </property>
+ </bean>
+ </property>
+</bean>]]></programlisting>
<para>Much of the above is boilerplate; below we'll touch on the key points
relevant to end users. There are two beans defined above, the
<literal>HAPartitionCacheHandler</literal> and the <literal>HAPartition</literal> itself.</para>
More information about the jboss-cvs-commits
mailing list