[
https://issues.apache.org/jira/browse/PDFBOX-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101938#comment-14101938
]
Petr Slaby commented on PDFBOX-2144:
------------------------------------
{quote}
Regarding the static configuration, what aspects of the configuration were you
expecting to change while PDFs are being processed? Are you talking about using
a specific FontProvider for a given PDF? If so why? This is certainly something
we could think about if I can get my head around the use case.
{quote}
Our application runs in an application server, many things can happen in
parallel there. Our configuration is stored in a database and can be changed
while the application is running. When changing the configuration, the
application might be in a middle of a rendering (or even in a middle of many
renderings). It is expected that the already running renderings finish the job
with the old configuration, while anything that has been started after the
commit of a new configuration uses the new one. The configuration contains many
settings, among others fonts to be used to render PDFs via PDFBox. I have to be
able to change the fonts available to FontProvider at runtime and in a way that
keeps the original configuration untouched for renderings that have already
been started.
> Provide a pluggable font manager
> --------------------------------
>
> Key: PDFBOX-2144
> URL: https://issues.apache.org/jira/browse/PDFBOX-2144
> Project: PDFBox
> Issue Type: Improvement
> Components: Rendering
> Reporter: Petr Slaby
> Attachments: FontManager.patch
>
>
> Our J2EE application has all fonts and resources configured and stored in its
> database. No files are accessed directly from file system or from system
> environment. To make PDFBox compatible with this philosophy, we need the
> FontManager in pdfbox and fontbox to be pluggable, e.g. as shown in the
> attached patch.
> The proposal defines a FontManager interface and default implementation which
> is the original one. FontManager then needs to be configured on and
> propagated from PDFStreamEngine and PageDrawer. It should also be
> configurable on PDFRenderer, which is not shown in the patch. There I would
> suggest to introduce a configuration object which would take care about all
> the current and future options of PDFRenderer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
