You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by je...@apache.org on 2003/05/15 18:06:39 UTC
cvs commit: xml-fop/src/documentation/content/xdocs graphics.xml running.xml
jeremias 2003/05/15 09:06:38
Modified: src/documentation/content/xdocs graphics.xml running.xml
Log:
Add a few words about the image cache and how to empty it.
Revision Changes Path
1.16 +15 -0 xml-fop/src/documentation/content/xdocs/graphics.xml
Index: graphics.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/graphics.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- graphics.xml 14 May 2003 17:56:58 -0000 1.15
+++ graphics.xml 15 May 2003 16:06:37 -0000 1.16
@@ -237,5 +237,20 @@
<p>If you need a higher apparent output resolution for bitmapped images, first make sure that at least one dimension of the image is defined in your XSL-FO input. Apart from that, resolution problems are in the image file itself, and must be corrected there: use or create a higher-resolution image file.</p>
<note>The explanation above describes only the basic default behavior. There are other attributes of the fo:external-graphic element that can affect the behavior described above.</note>
</section>
+ <section id="caching">
+ <title>Image caching</title>
+ <p>
+ FOP caches images between runs. The URL is used as a key to identify images which means that when
+ a particular URL appears again, the image is taken from the cache. If you have a servlet that
+ generates a different image each time it is called with the same URL you need to use a constantly
+ changing dummy parameter on the URL to avoid caching.
+ </p>
+ <p>
+ Currently, the images are not automatically released when an OutOfMemoryError is imminent. The
+ image cache can grow to a considerable size over time when a lot of different URLs are in use.
+ Starting with version 0.20.5 you can call <code>org.apache.fop.image.FopImageFactory.resetCache()</code>
+ to manually empty the cache. Image caching will be improved as part of our redesign effort.
+ </p>
+ </section>
</body>
</document>
1.12 +5 -0 xml-fop/src/documentation/content/xdocs/running.xml
Index: running.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/running.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- running.xml 5 May 2003 23:37:38 -0000 1.11
+++ running.xml 15 May 2003 16:06:38 -0000 1.12
@@ -156,6 +156,11 @@
With headers and footers, consider integrating them as normal table rows, or, if they are used at page breaks, try to put the information into static content.
You can then use markers to change them.
</li>
+ <li>
+Clear the image cache. At the moment, images in the cache are not released automatically when an OutOfMemoryError is imminent.
+Starting with version 0.20.5 however, you can call <code>org.apache.fop.image.FopImageFactory.resetCache()</code> to empty the
+<jump href="graphics.html#caching">image cache</jump>.
+ </li>
</ul>
<p>
There are currently some bugs which cause FOP to go into a nonterminating loop, which will also often result in a memory overflow.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org