If anyone is interested they can apply this to xdocs/faq.fml
Index: faq.fml
===================================================================
--- faq.fml (revision 538091)
+++ faq.fml (working copy)
@@ -100,6 +100,14 @@
to see if any property key in
the cache.ccf is
defined in the system
properties. If so, the system
value will be used.
+ So you can use:
+
"-Djcs.auxiliary.DC.attributes.DiskPath=value" or
+
-DMY_SYSTEM_PROPERTY_MAX_SIZE=100 and change the config file to have
+
jcs.default.cacheattributes.MaxObjects=${MY_SYSTEM_PROPERTY_MAX_SIZE}
+
+ NOTE: This does not work for
the RemoteCache.
+
+
</p>
</answer>
</faq>
@@ -108,6 +116,24 @@
<part id="general-questions">
<title>General Questions</title>
+
+ <faq id="source-code">
+ <question>Where can I get the example code?</question>
+ <answer>
+ <p>
+ The unit tests cover most of
the functionality. Have a
+ look at the
+ <a
+
href="http://svn.apache.org/viewvc/jakarta/jcs/trunk/src/test/org/apache/jcs/";>
+ test code
+ </a>
+ in subversion.
+
+ </p>
+ </answer>
+ </faq>
+
+
<faq id="jcs-vs-ehcache">
<question>Is JCS faster than EHCache?</question>
<answer>
@@ -154,6 +180,7 @@
</p>
</answer>
</faq>
+
<faq id="compiling-source">
<question>How do I compile the source?</question>
<answer>
@@ -206,6 +233,23 @@
</answer>
</faq>
+ <faq id="element-keys">
+ <question>How do I get all the keys?</question>
+ <answer>
+ <p>
+
+ JCS does not provide such a
method. Not all
+ auxiliaries can support it and
it isn't clear how the
+ cache should behave if the
data is in a remote node.
+ The remote server, for
instance, may have millions of
+ keys that are not stored
locally. Also, not all disk
+ caches will be able to return
a list of keys.
+
+ </p>
+ </answer>
+ </faq>
+
+
<faq id="hierarchical-removal">
<question>
Can I remove all items beginning with
part of a key?
@@ -283,4 +327,4 @@
</faq>
</part>
-</faqs>
\ No newline at end of file
+</faqs>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
