From 575d345ab749902b13fd2b76c5f80335c2067273 Mon Sep 17 00:00:00 2001
From: Jeremias Maerki <jeremias@apache.org>
Date: Tue, 21 Oct 2008 10:13:27 +0000
Subject: [PATCH] Reluctantly added a note about how to clear the image cache.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@706570 13f79535-47bb-0310-9956-ffa450edef68
---
 src/documentation/content/xdocs/0.95/graphics.xml  | 8 ++++++--
 src/documentation/content/xdocs/trunk/graphics.xml | 8 ++++++--
 2 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/src/documentation/content/xdocs/0.95/graphics.xml b/src/documentation/content/xdocs/0.95/graphics.xml
index dce05aa47..5ecca1ea8 100644
--- a/src/documentation/content/xdocs/0.95/graphics.xml
+++ b/src/documentation/content/xdocs/0.95/graphics.xml
@@ -554,10 +554,14 @@
         changing dummy parameter on the URI to avoid caching.
       </p>
       <p>
-        The image cache has been improved considerably in the redesigned code. Therefore, a 
-        resetCache() method like in earlier versions of FOP has become unnecessary. If you 
+        The image cache has been improved considerably in the redesigned code. Therefore,
+        resetting the image cache should be a thing of the past. If you 
         still experience OutOfMemoryErrors, please notify us.
       </p>
+      <p>
+        If all else fails, the image cache can be cleared like this:
+        <code>fopFactory.getImageManager().getCache().clearCache();</code>
+      </p>
     </section>
   </body>
 </document>
diff --git a/src/documentation/content/xdocs/trunk/graphics.xml b/src/documentation/content/xdocs/trunk/graphics.xml
index dce05aa47..5ecca1ea8 100644
--- a/src/documentation/content/xdocs/trunk/graphics.xml
+++ b/src/documentation/content/xdocs/trunk/graphics.xml
@@ -554,10 +554,14 @@
         changing dummy parameter on the URI to avoid caching.
       </p>
       <p>
-        The image cache has been improved considerably in the redesigned code. Therefore, a 
-        resetCache() method like in earlier versions of FOP has become unnecessary. If you 
+        The image cache has been improved considerably in the redesigned code. Therefore,
+        resetting the image cache should be a thing of the past. If you 
         still experience OutOfMemoryErrors, please notify us.
       </p>
+      <p>
+        If all else fails, the image cache can be cleared like this:
+        <code>fopFactory.getImageManager().getCache().clearCache();</code>
+      </p>
     </section>
   </body>
 </document>
-- 
2.39.5