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 "Matteo Franci (Jira)" <ji...@apache.org> on 2022/11/20 18:08:00 UTC
[jira] [Updated] (FOP-3109) Custom ResourceResolver seems to be ignored in version 2.7+
[ https://issues.apache.org/jira/browse/FOP-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matteo Franci updated FOP-3109:
-------------------------------
Description:
It's the first time I open an issue on Apache JIRA. I read the guidelines but I hope I did not make mistakes.
When creating a FopFactory with a custom ResourceResolver, the resolver seems to be ignored in Apache FOP 2.7 e 2.8.
The same code apperead to work properly in Apache FOP 2.6.
{code:java}
ResourceResolver resolver = new ClassLoaderResourceResolver();
FopFactoryBuilder builder = new FopFactoryBuilder(new File(".").toURI(), resolver );
builder = builder.setConfiguration(new DefaultConfigurationBuilder().build(fopConfigStream));
FopFactory fopFactory = builder.build(); {code}
Here is a proof of concept with a custom ResourceResolver loading font from the class loader when the path starts with classpath://
[https://github.com/fugerit79/fop-custom-resource-resolver-poc]
was:
When creating a FopFactory with a custom ResourceResolver, the resolver seems to be ignored in Apache FOP 2.7 e 2.8.
The same code apperead to work properly in Apache FOP 2.6.
{code:java}
ResourceResolver resolver = new ClassLoaderResourceResolver();
FopFactoryBuilder builder = new FopFactoryBuilder(new File(".").toURI(), resolver );
builder = builder.setConfiguration(new DefaultConfigurationBuilder().build(fopConfigStream));
FopFactory fopFactory = builder.build(); {code}
Here is a proof of concept with a custom ResourceResolver loading font from the class loader when the path starts with classpath://
https://github.com/fugerit79/fop-custom-resource-resolver-poc
> Custom ResourceResolver seems to be ignored in version 2.7+
> -----------------------------------------------------------
>
> Key: FOP-3109
> URL: https://issues.apache.org/jira/browse/FOP-3109
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf, unqualified
> Affects Versions: 2.7, 2.8
> Environment: Tested on :
> JDK 1.8.0_333 and JDK 11.0.16
> Apache Maven 3.8.6
> Windows 10 and Ubuntu 22.04
> Reporter: Matteo Franci
> Priority: Major
>
> It's the first time I open an issue on Apache JIRA. I read the guidelines but I hope I did not make mistakes.
> When creating a FopFactory with a custom ResourceResolver, the resolver seems to be ignored in Apache FOP 2.7 e 2.8.
> The same code apperead to work properly in Apache FOP 2.6.
> {code:java}
> ResourceResolver resolver = new ClassLoaderResourceResolver();
> FopFactoryBuilder builder = new FopFactoryBuilder(new File(".").toURI(), resolver );
> builder = builder.setConfiguration(new DefaultConfigurationBuilder().build(fopConfigStream));
> FopFactory fopFactory = builder.build(); {code}
>
> Here is a proof of concept with a custom ResourceResolver loading font from the class loader when the path starts with classpath://
> [https://github.com/fugerit79/fop-custom-resource-resolver-poc]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)