[jboss-cvs] JBossAS SVN: r97674 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Dec 10 01:36:07 EST 2009
Author: laubai
Date: 2009-12-10 01:36:06 -0500 (Thu, 10 Dec 2009)
New Revision: 97674
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache.xml
Log:
Added JBPAPP-2649 changes to Admin and Config Guide.
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache.xml 2009-12-10 06:35:35 UTC (rev 97673)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_JBoss_Cache.xml 2009-12-10 06:36:06 UTC (rev 97674)
@@ -14,7 +14,7 @@
</para>
<para>Users considering deploying JBoss Cache for direct use by their own
application are strongly encouraged to read the JBoss Cache
- documentation available at http://www.jboss.org/jbosscache.</para>
+ documentation available at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>.</para>
<para>See also <xref linkend="clustering-blocks-jbc"/> for information on
how the standard JBoss Enterprise Application Platform clustered services use JBoss Cache.</para>
@@ -31,7 +31,7 @@
provide a brief overview of some of the key configuration choices. This
is by no means a complete discussion; for full details users interested in moving
beyond the default configurations are encouraged to read the JBoss Cache
- documentation available at http://www.jboss.org/jbosscache.</para>
+ documentation available at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>.</para>
<para>Most JBoss Cache configuration examples in this section use the
JBoss Microcontainer schema for building up an <literal>org.jboss.cache.config.Configuration</literal>
@@ -574,7 +574,7 @@
all of the available options. For details on configuring it for
JPA/Hibernate caching, see the Eviction chapter in the "Using JBoss Cache
as a Hibernate Second Level Cache" guide at
- http://www.jboss.org/jbossclustering/docs/hibernate-jbosscache-guide-3.pdf.
+ <ulink url="http://www.jboss.org/jbossclustering/docs/hibernate-jbosscache-guide-3.pdf">http://www.jboss.org/jbossclustering/docs/hibernate-jbosscache-guide-3.pdf</ulink>.
For web session caches, eviction should not be configured; the
distributable session manager handles eviction itself. For EJB 3
SFSB caches, stick with the eviction configuration in the Enterprise Application Platform's standard
@@ -770,15 +770,15 @@
<itemizedlist>
<listitem><para><emphasis role="bold">buddyReplicationEnabled</emphasis>
- -- <literal>true</literal> if you want buddy replication; <literal>false</literal>
+ — <literal>true</literal> if you want buddy replication; <literal>false</literal>
if data should be replicated to all nodes in the cluster, in which case
none of the other buddy replication configurations matter.</para>
</listitem>
<listitem><para><emphasis role="bold">numBuddies</emphasis>
- -- to how many backup nodes should each node replicate its state.</para>
+ — to how many backup nodes should each node replicate its state.</para>
</listitem>
<listitem><para><emphasis role="bold">buddyPoolName</emphasis>
- -- allows logical subgrouping of nodes within the cluster; if possible,
+ — allows logical subgrouping of nodes within the cluster; if possible,
buddies will be chosen from nodes in the same buddy pool.</para>
</listitem>
</itemizedlist>
@@ -965,11 +965,11 @@
<section id="jbosscache-custom-deployment-service.xml">
<title>Deployment Via a <literal>-service.xml</literal> File</title>
- <para>As in JBoss 4, you can also deploy a JBoss Cache instance as
+ <para>As in JBoss 4.x, you can also deploy a JBoss Cache instance as
an MBean service via a <literal>-service.xml</literal> file.
- The primary difference from JBoss 4 is the value of the <literal>code</literal>
- attribute in the <literal>mbean</literal> element. In JBoss 4, this
- was <literal>org.jboss.cache.TreeCache</literal>; in JBoss 5 it is
+ The primary difference from JBoss 4.x is the value of the <literal>code</literal>
+ attribute in the <literal>mbean</literal> element. In JBoss 4.x, this
+ was <literal>org.jboss.cache.TreeCache</literal>; in JBoss 5.x it is
<literal>org.jboss.cache.jmx.CacheJmxWrapper</literal>. Here's an
example:</para>
More information about the jboss-cvs-commits
mailing list