Author: asmuts
Date: Sun Mar 18 18:20:09 2007
New Revision: 519781
URL: http://svn.apache.org/viewvc?view=rev&rev=519781
Log:
FIXED JCS-19
Applied xdoc spelling error patch supplied by Michael Stevens.
Modified:
jakarta/jcs/trunk/src/test-conf/log4j.properties
jakarta/jcs/trunk/xdocs/BDBJEDiskCache.ccf
jakarta/jcs/trunk/xdocs/BasicJCSConfiguration.xml
jakarta/jcs/trunk/xdocs/ElementAttributes.xml
jakarta/jcs/trunk/xdocs/IndexedDiskAuxCache.xml
jakarta/jcs/trunk/xdocs/JCSandJCACHE.xml
jakarta/jcs/trunk/xdocs/JCSvsEHCache.xml
jakarta/jcs/trunk/xdocs/JDBCDiskCache.xml
jakarta/jcs/trunk/xdocs/LateralTCPAuxCache.xml
jakarta/jcs/trunk/xdocs/LateralTCPProperties.xml
jakarta/jcs/trunk/xdocs/LateralUDPDiscovery.xml
jakarta/jcs/trunk/xdocs/LocalCacheConfig.xml
jakarta/jcs/trunk/xdocs/MySQLDiskCacheProperties.xml
jakarta/jcs/trunk/xdocs/Plugins.xml
jakarta/jcs/trunk/xdocs/RemoteAuxCache.xml
jakarta/jcs/trunk/xdocs/RemoteCacheProperties.xml
jakarta/jcs/trunk/xdocs/UsingJCSBasicWeb.xml
jakarta/jcs/trunk/xdocs/faq.fml
jakarta/jcs/trunk/xdocs/getting_started/intro.xml
jakarta/jcs/trunk/xdocs/index.xml
Modified: jakarta/jcs/trunk/src/test-conf/log4j.properties
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/src/test-conf/log4j.properties?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/src/test-conf/log4j.properties (original)
+++ jakarta/jcs/trunk/src/test-conf/log4j.properties Sun Mar 18 18:20:09 2007
@@ -16,7 +16,7 @@
log4j.appender.stdout.layout.ConversionPattern=%d %p [%c{1}] - <%m>%n
log4j.appender.logfile=org.apache.log4j.RollingFileAppender
-log4j.appender.logfile.File=target/test-sandbox/logs/jcs.log
+log4j.appender.logfile.File=target/jcs.log
log4j.appender.logfile.MaxFileSize=5MB
# Keep three backup files
log4j.appender.logfile.MaxBackupIndex=3
Modified: jakarta/jcs/trunk/xdocs/BDBJEDiskCache.ccf
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/BDBJEDiskCache.ccf?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/BDBJEDiskCache.ccf (original)
+++ jakarta/jcs/trunk/xdocs/BDBJEDiskCache.ccf Sun Mar 18 18:20:09 2007
@@ -31,7 +31,7 @@
<subsection name="Configuration">
<p>
- The simple configuration and is done in the auxiliary
+ The configuration is simple and is done in the auxiliary
cache section of the <code>cache.ccf</code> configuration file.
In the example below, I created a Berkeley DB Auxiliary Cache
referenced by <code>BDBDC</code>. It uses files located in the
Modified: jakarta/jcs/trunk/xdocs/BasicJCSConfiguration.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/BasicJCSConfiguration.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/BasicJCSConfiguration.xml (original)
+++ jakarta/jcs/trunk/xdocs/BasicJCSConfiguration.xml Sun Mar 18 18:20:09 2007
@@ -111,7 +111,7 @@
</subsection>
<subsection name="A few comments on configuration">
<p>
- Auxiliary definitions are like log4j appenders, they are defines
+ Auxiliary definitions are like log4j appenders, they are defined
and then associated with a region like a log4j category.
</p>
<p>
Modified: jakarta/jcs/trunk/xdocs/ElementAttributes.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/ElementAttributes.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/ElementAttributes.xml (original)
+++ jakarta/jcs/trunk/xdocs/ElementAttributes.xml Sun Mar 18 18:20:09 2007
@@ -22,7 +22,7 @@
The configuration below can be put in
the cache.ccf
configuration file. It establishes the
default
behavior for all regions. A region can
override
- these defaults and an individual
element can overide
+ these defaults and an individual
element can override
these defaults and the region settings.
</p>
<source>
Modified: jakarta/jcs/trunk/xdocs/IndexedDiskAuxCache.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/IndexedDiskAuxCache.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/IndexedDiskAuxCache.xml (original)
+++ jakarta/jcs/trunk/xdocs/IndexedDiskAuxCache.xml Sun Mar 18 18:20:09 2007
@@ -74,7 +74,7 @@
<subsection name="Configuration">
<p>
- The simple configuration and is done in
the
+ Configuration is simple and is done in
the
auxiliary cache section of the
<code>cache.ccf</code>
configuration file. In the example
below, I created
Modified: jakarta/jcs/trunk/xdocs/JCSandJCACHE.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/JCSandJCACHE.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/JCSandJCACHE.xml (original)
+++ jakarta/jcs/trunk/xdocs/JCSandJCACHE.xml Sun Mar 18 18:20:09 2007
@@ -87,7 +87,7 @@
I started to support <code>ObjectNotFoundExceptions</code> for
failed gets but the overhead and cumbersome coding needed to
surround a simple get method is ridiculous. Instead the JCS
- return null.
+ returns null.
</p>
</subsection>
<subsection name="Cache Loaders">
Modified: jakarta/jcs/trunk/xdocs/JCSvsEHCache.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/JCSvsEHCache.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/JCSvsEHCache.xml (original)
+++ jakarta/jcs/trunk/xdocs/JCSvsEHCache.xml Sun Mar 18 18:20:09 2007
@@ -450,7 +450,7 @@
The ehcache disk version is very simple. It
puts an
unlimited number of items in a temporary store.
You can
easily fill this up and run out of memory. You
can put
- items into JCS prugatory faster than they can
be gc's
+ items into JCS purgatory faster than they can
be gc'd
but it is much more difficult. The EH store is
then
flushed to disk every 200ms. While EH is
flushing the
entire disk cache blocks!
Modified: jakarta/jcs/trunk/xdocs/JDBCDiskCache.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/JDBCDiskCache.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/JDBCDiskCache.xml (original)
+++ jakarta/jcs/trunk/xdocs/JDBCDiskCache.xml Sun Mar 18 18:20:09 2007
@@ -12,7 +12,7 @@
The JDBC disk cache uses a relational database
such as
MySQL as a persistent store. It works with
Oracle, MySQL
and HSQL. The cache elements are serialized and
written
- into a BLOB. Mutliple regions can share a
single table.
+ into a BLOB. Multiple regions can share a
single table.
You can define multiple, differently configured
JDBC
disk caches in one JCS instance. This allows
you to use
different tables for different cache regions.
Modified: jakarta/jcs/trunk/xdocs/LateralTCPAuxCache.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/LateralTCPAuxCache.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/LateralTCPAuxCache.xml (original)
+++ jakarta/jcs/trunk/xdocs/LateralTCPAuxCache.xml Sun Mar 18 18:20:09 2007
@@ -13,7 +13,7 @@
The TCP Lateral Auxiliary Cache is an optional plug in for the
JCS. It is primarily intended to broadcast puts and removals to
other local caches, though it can also get cached objects. It
- functions by opening up a <code> SocketServer</code> that
+ functions by opening up a <code>SocketServer</code> that
listens to a configurable port and by creating
<code>Socket</code> connections with other local cache
<code>SocketServers</code>. It can be configured to connect to
@@ -65,7 +65,7 @@
<subsection name="Send Only Configuration">
<p>
You can configure the TCP lateral cache to operate
- in send only more by setting the <code>Receive</code> attribute
+ in send only mode by setting the <code>Receive</code> attribute
to false. By default the receive attribute is true.
When it is set to false, the lateral cache will not
establish a socket server.
Modified: jakarta/jcs/trunk/xdocs/LateralTCPProperties.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/LateralTCPProperties.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/LateralTCPProperties.xml (original)
+++ jakarta/jcs/trunk/xdocs/LateralTCPProperties.xml Sun Mar 18 18:20:09 2007
@@ -56,7 +56,7 @@
set receive to false if you just need to broadcast to other
caches. If you
have a feed data parser, that doesn't need to receive updates,
but you
do want it to send invalidation messages, then you would set
receive to false.
- If receive is false, teh discovery service, if enabled, will
only listen.
+ If receive is false, the discovery service, if enabled, will
only listen.
</td>
<td>N</td>
<td>true</td>
Modified: jakarta/jcs/trunk/xdocs/LateralUDPDiscovery.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/LateralUDPDiscovery.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/LateralUDPDiscovery.xml (original)
+++ jakarta/jcs/trunk/xdocs/LateralUDPDiscovery.xml Sun Mar 18 18:20:09 2007
@@ -16,7 +16,7 @@
</p>
<p>
On startup each lateral will issue a special message requesting
a
- broadcast from the others caches. Normal broadcasts occur
every
+ broadcast from the other caches. Normal broadcasts occur every
30 seconds. (This is to be made configurable.) Regions that
don't
receive, are running in send only mode, don't broadcast
anything but requests.
</p>
Modified: jakarta/jcs/trunk/xdocs/LocalCacheConfig.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/LocalCacheConfig.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/LocalCacheConfig.xml (original)
+++ jakarta/jcs/trunk/xdocs/LocalCacheConfig.xml Sun Mar 18 18:20:09 2007
@@ -64,7 +64,7 @@
<p>
The most important line is
<code>jcs.default=DC,Rfailover</code>. This tells the cache
- what auxiliary caches should be used. Auxialiary caches are
+ what auxiliary caches should be used. Auxiliary caches are
configured in the third section of the <code>cache.ccf</code>
and are referenced in a comma separated list. You can add as
many auxiliary caches as you want, but the behavior of remote
Modified: jakarta/jcs/trunk/xdocs/MySQLDiskCacheProperties.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/MySQLDiskCacheProperties.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/MySQLDiskCacheProperties.xml (original)
+++ jakarta/jcs/trunk/xdocs/MySQLDiskCacheProperties.xml Sun Mar 18 18:20:09
2007
@@ -12,7 +12,7 @@
<p>
The MySQL Disk Cache uses all of the JDBC Disk
Cache
properties. It adds a few of its own. The
following
- properties on apply to the MySQL Disk Cache
plugin.
+ properties only apply to the MySQL Disk Cache
plugin.
</p>
<subsection name="MySQL Disk Configuration Properties">
@@ -31,7 +31,7 @@
table. If none is
supplied, then no
optimizations will be
performed.
- In the future we can
add a chron like
+ In the future we can
add a cron like
scheduling system. This
was created to meet
a pressing need to
optimize fragmented
MyISAM tables. When the
table becomes
Modified: jakarta/jcs/trunk/xdocs/Plugins.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/Plugins.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/Plugins.xml (original)
+++ jakarta/jcs/trunk/xdocs/Plugins.xml Sun Mar 18 18:20:09 2007
@@ -14,8 +14,8 @@
</p>
<p>
There are four types of auxiliaries: (1) memory, (2) disk, (3) lateral,
and (4) remote. Each region is required to have one and only one
memory auxiliary. No other auxiliaries are required and any possible
combination of disk, lateral, and remote auxiliaries is allowed. If you
- Do not want to store items in memory, then the maximum size for the
memory
- Caches can be set to 0 on a per region basis.
+ do not want to store items in memory, then the maximum size for the
memory
+ caches can be set to 0 on a per region basis.
</p>
</section>
@@ -42,11 +42,11 @@
<section name="Lateral Plugins">
<p>
- JCS provides two recommended lateral distribution options: TCP socket
server distribution and JGroups (or JavaGroups). There are also several
other experiemental lateral distribution auxiliaries using servlets, UDP,
and xmlrpc.
+ JCS provides two recommended lateral distribution options: TCP socket
server distribution and JGroups (or JavaGroups). There are also several
other experimental lateral distribution auxiliaries using servlets, UDP,
and xmlrpc.
</p>
</section>
- <section name="Remote Plugins">
+ <section name="Remote Plugins">
<p>
JCS also provides an RMI based remote server to manage distribution of
cached data.
</p>
Modified: jakarta/jcs/trunk/xdocs/RemoteAuxCache.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/RemoteAuxCache.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/RemoteAuxCache.xml (original)
+++ jakarta/jcs/trunk/xdocs/RemoteAuxCache.xml Sun Mar 18 18:20:09 2007
@@ -30,7 +30,7 @@
<p>
If there is an error connecting to the remote
server or
if an error occurs in transmission, the client
will
- retry for a configurable number of tires before
moving
+ retry for a configurable number of tries before
moving
into a failover-recovery mode. If failover
servers are
configured the remote cache clients will try to
register
with other failover servers in a sequential
order. If a
@@ -305,9 +305,9 @@
</p>
<p>
JCS provides a convenient startup
servlet for this
- purpose. It will start the registery
and bind the
+ purpose. It will start the registry and
bind the
JCS server to the registry. To use the
startup
- servlet, add the following to the
web.xml file add
+ servlet, add the following to the
web.xml file and
make sure you have the remote.cache.ccf
file in the
WEB-INF/classes directly of your war
file.
</p>
Modified: jakarta/jcs/trunk/xdocs/RemoteCacheProperties.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/RemoteCacheProperties.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/RemoteCacheProperties.xml (original)
+++ jakarta/jcs/trunk/xdocs/RemoteCacheProperties.xml Sun Mar 18 18:20:09 2007
@@ -45,7 +45,7 @@
<td>
This is the port on
which the client will
receive callbacks from
the remote server. If
- it is not spedified,
then some port in the
+ it is not specified,
then some port in the
default range used by
RMI will be the
callback port.
</td>
@@ -120,7 +120,7 @@
<td>
The number of elements
the zombie queue will
hold. This queue is
used to store events if
- we * loose our
conenction with the server.
+ we lose our connection
with the server.
</td>
<td>N</td>
<td>1000</td>
Modified: jakarta/jcs/trunk/xdocs/UsingJCSBasicWeb.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/UsingJCSBasicWeb.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/UsingJCSBasicWeb.xml (original)
+++ jakarta/jcs/trunk/xdocs/UsingJCSBasicWeb.xml Sun Mar 18 18:20:09 2007
@@ -321,7 +321,7 @@
<p>
The next step will be to select an appropriate
distribution layer. If you have a back-end server
- running an apserver or scripts or are running multiple
+ running an appserver or scripts or are running multiple
webserver VMs on one machine, you might want to use
the centralized <a href="RemoteAuxCache.html">remote
cache</a>. The lateral cache would be fine, but since
Modified: jakarta/jcs/trunk/xdocs/faq.fml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/faq.fml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/faq.fml (original)
+++ jakarta/jcs/trunk/xdocs/faq.fml Sun Mar 18 18:20:09 2007
@@ -91,7 +91,7 @@
<faq id="configuration-system-properties">
<question>
- Can JCS use system propeties during
configuration?
+ Can JCS use system properties during
configuration?
</question>
<answer>
<p>
@@ -147,9 +147,9 @@
href="http://svn.apache.org/viewcvs.cgi/jakarta/jcs/trunk/";>
here
</a>
- or get the source code from subversion
with svn co
-
http://svn.apache.org/repos/asf/jakarta/jcs/trunk.
- The tagged releases are available with
svn co. ex.
+ or get the source code from subversion
with <code>svn co
+
http://svn.apache.org/repos/asf/jakarta/jcs/trunk</code>.
+ The tagged releases are available with
<code>svn co.</code> ex.
http://svn.apache.org/repos/asf/jakarta/jcs/tags/jcs_1_2_7_0
</p>
</answer>
@@ -208,7 +208,7 @@
<faq id="hierarchical-removal">
<question>
- Can I remove all items begging with part of a
key?
+ Can I remove all items beginning with part of a
key?
</question>
<answer>
<p>
@@ -216,7 +216,7 @@
auxiliaries will have to iterate over
their keysets.
Although all the auxiliaries honor
this, it is not
part of the auxiliary API. There is no
method along
- the lins of "removeStartingWith", but
all the remove
+ the lines of "removeStartingWith", but
all the remove
methods can do it.
</p>
<p>
Modified: jakarta/jcs/trunk/xdocs/getting_started/intro.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/getting_started/intro.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/getting_started/intro.xml (original)
+++ jakarta/jcs/trunk/xdocs/getting_started/intro.xml Sun Mar 18 18:20:09 2007
@@ -59,7 +59,7 @@
<section name="STEP 2: Download JCS">
<p>
- Download the latest version of JCS. The latests
JCS
+ Download the latest version of JCS. The latest
JCS
builds are located
<a
href="http://svn.apache.org/viewcvs.cgi/jakarta/jcs/trunk/tempbuild/";>
@@ -188,7 +188,7 @@
<section name="STEP 5: Programming to JCS">
<p>
JCS provides a convenient class that should
meet all
- your needs. It is called, appropriately engough,
+ your needs. It is called, appropriately enough,
<code>org.apache.jcs.JCS</code>
</p>
<p>
Modified: jakarta/jcs/trunk/xdocs/index.xml
URL:
http://svn.apache.org/viewvc/jakarta/jcs/trunk/xdocs/index.xml?view=diff&rev=519781&r1=519780&r2=519781
==============================================================================
--- jakarta/jcs/trunk/xdocs/index.xml (original)
+++ jakarta/jcs/trunk/xdocs/index.xml Sun Mar 18 18:20:09 2007
@@ -70,7 +70,7 @@
</p>
<p>
The JCS jar provides production ready
implementations of
- each of the four types of caches. In addtion to
the core
+ each of the four types of caches. In addition
to the core
four, JCS also provides additional plugins of
each type.
</p>
@@ -181,7 +181,7 @@
provided by JCS can scale into the tens of
servers. In a
well-designed service oriented architecture,
JCS can be
used in a high demand service with numerous
nodes. This
- would not be possible is the distribution
mechanism were
+ would not be possible if the distribution
mechanism were
transactional.
</p>
<p>
@@ -190,7 +190,7 @@
so it can just send a field or two fewer over
the wire.
</p>
<p>
- JCS is not fork, an offshoot, a branch, or any
other
+ JCS is not a fork, an offshoot, a branch, or
any other
derivation of JCS. Nor is JCS named after
another
library. JCS is a mature project that has been
under
development and in use since 2001. Over the
years JCS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
