You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Martin Wegner (JIRA)" <ji...@apache.org> on 2015/06/03 18:44:39 UTC
[jira] [Updated] (FOP-2480) Since FOP 2.0 it is not possible to
load embedded fonts from a JAR
[ https://issues.apache.org/jira/browse/FOP-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Wegner updated FOP-2480:
-------------------------------
Description:
In FOP 1.1 it was possible to load embedded fonts (relative path in the fop.xconf) from a JAR by using a custom URIResolver and setting it (fopFactory.setURIResolver(fileResolver)) before loading the fop.xconf. The custom URIResolver was used while parsing the fop.xconf and resolving relative paths.
FOP 2.0 does not use the given resolver. It uses resolveFromBase() from the InternalResourceResolver. The method resolveFromBase() calls resolve() from the base URI. Because it is impossible to overwrite URI or InternalResourceResolver there is no chance to load embedded fonts (relative path in the fop.xconf) from a JAR by using a custom URIResolver.
was:
In FOP 1.1 it was possible to load embedded fonts (relative path in the fop.xconf) from a JAR by using a custom URIResolver and setting it (fopFactory.setURIResolver(fileResolver);) before loading the fop.xconf. The custom URIResolver was used while parsing the fop.xconf and resolving relative paths.
FOP 2.0 does not use the given resolver. It uses resolveFromBase() from the InternalResourceResolver. The method resolveFromBase() calls resolve() from the base URI. Because it is impossible to overwrite URI or InternalResourceResolver there is no chance to load embedded fonts (relative path in the fop.xconf) from a JAR by using a custom URIResolver.
> Since FOP 2.0 it is not possible to load embedded fonts from a JAR
> ------------------------------------------------------------------
>
> Key: FOP-2480
> URL: https://issues.apache.org/jira/browse/FOP-2480
> Project: FOP
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Martin Wegner
>
> In FOP 1.1 it was possible to load embedded fonts (relative path in the fop.xconf) from a JAR by using a custom URIResolver and setting it (fopFactory.setURIResolver(fileResolver)) before loading the fop.xconf. The custom URIResolver was used while parsing the fop.xconf and resolving relative paths.
> FOP 2.0 does not use the given resolver. It uses resolveFromBase() from the InternalResourceResolver. The method resolveFromBase() calls resolve() from the base URI. Because it is impossible to overwrite URI or InternalResourceResolver there is no chance to load embedded fonts (relative path in the fop.xconf) from a JAR by using a custom URIResolver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)