You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Tilman Hausherr (JIRA)" <ji...@apache.org> on 2019/02/05 19:13:00 UTC
[jira] [Updated] (PDFBOX-4231) cache file fallback if not writable
[ https://issues.apache.org/jira/browse/PDFBOX-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tilman Hausherr updated PDFBOX-4231:
------------------------------------
Fix Version/s: 3.0.0 PDFBox
2.0.14
> cache file fallback if not writable
> -----------------------------------
>
> Key: PDFBOX-4231
> URL: https://issues.apache.org/jira/browse/PDFBOX-4231
> Project: PDFBox
> Issue Type: Improvement
> Reporter: Michael Brackx
> Priority: Major
> Fix For: 2.0.14, 3.0.0 PDFBox
>
>
> Fallback to the next file location if the current location for .pdfbox.cache is not writable.
> Currently there is a fallback from pdfbox.fontcache to user.home to java.io.tmpdir as directory to write .pdfbox.cache, but this is only on the level of if the system property is defined.
> It would be nice to fallback to the next directory if the file is not writable in a directory.
> Without config and on a system where user.home is not writable pdfbox is quite slow, as the caching is tried each time.
> Usually java.io.tmpdir is writable, so this would provide better performance out of the box.
> The workaound is to configure the pdfbox.fontcache system property.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org