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 "MH (JIRA)" <ji...@apache.org> on 2015/07/03 16:46:05 UTC
[jira] [Comment Edited] (FOP-2495) Embedding: missing migration
documentation from FOP 1.x
[ https://issues.apache.org/jira/browse/FOP-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612047#comment-14612047 ]
MH edited comment on FOP-2495 at 7/3/15 2:45 PM:
-------------------------------------------------
E.g. URIResolver: FOP 1.0:
FoUserAgent.setURIResolver(javax.xml.transform.URIResolver)
In FOP 2.0 (https://xmlgraphics.apache.org/fop/2.0/embedding.html):
---------
"Set a URIResolver for custom URI resolution. By supplying a JAXP URIResolver you can add custom URI resolution functionality to FOP. For example:
// myResourceResolver is a org.apache.xmlgraphics.io.ResourceResolver
FopFactoryBuilder builder = new FopFactoryBuilder(baseURI, myResourceResolver);"
------------
... but FopFactoryBuilder does not accept javax.xml.transform.URIResolver but requires a org.apache.xmlgraphics.io.ResourceResolver that is an interface ... probably org.apache.fop.apps.io.InternalResourceResolver that has no API to use a javax.xml.transform.URIResolver
Can you please submit an example to set an URIResolver just like
FoUserAgent.setURIResolver()
in FOP 1.0/1.1? Thank you!
was (Author: mhilpert):
E.g. URIResolver: FOP 1.0:
FoUserAgent.setURIResolver(javax.xml.transform.URIResolver)
In FOP 2.0 (https://xmlgraphics.apache.org/fop/2.0/embedding.html):
---------
"Set a URIResolver for custom URI resolution. By supplying a JAXP URIResolver you can add custom URI resolution functionality to FOP. For example:
// myResourceResolver is a org.apache.xmlgraphics.io.ResourceResolver
FopFactoryBuilder builder = new FopFactoryBuilder(baseURI, myResourceResolver);"
------------
... but FopFactoryBuilder does not accept javax.xml.transform.URIResolver but requires a org.apache.xmlgraphics.io.ResourceResolver that is an interface ... probably org.apache.fop.apps.io.InternalResourceResolver that has no API to use a javax.xml.transform.URIResolver
Oh boy ...
> Embedding: missing migration documentation from FOP 1.x
> -------------------------------------------------------
>
> Key: FOP-2495
> URL: https://issues.apache.org/jira/browse/FOP-2495
> Project: FOP
> Issue Type: Bug
> Components: documentation
> Affects Versions: 2.0
> Environment: WIndows, Java 8, FOP 1.0
> Reporter: MH
> Priority: Blocker
> Labels: documentation
>
> Because of bug FOP-2177 we couldn't upgrade form FOP 1.0 to FOP 1.1. FOP 2.0 has solved this bug (tested with standalone FOP scripts).
> Now we would like to upgrade our Java code from FOP 1.0 to FOP 2.0. The Upgrading page (https://xmlgraphics.apache.org/fop/2.0/upgrading.html) says "You should encounter very few issues in upgrading from FOP 1.0, except as noted in the following: ...". The truth is completely different: starting by replacing fop.jar, our code gets dozens of compiler errors! Many methods are simply gone:
> FopFactory.newInstance()
> FoUserAgent.setBaseURL(String);
> FopFactory.getFontManager().setFontBaseURL(String)
> FopFactory.setURIResolver(URIResolver);
> etc.
> The javadocs from 1.1 to 2.0 simple changed - no deprecated methods, no hints how to replace old methods.
> The FOP 2.0 embedding page (https://xmlgraphics.apache.org/fop/2.0/embedding.html) just shows simple examples to start from the ground. I can't find any migration help how to replace old code.
> E.g. how can I set the font base? FopFactory.getFontManager().setFontBaseURL(String) is gone and I can't find any equivalent code for FOP 2.0!
> This is a major bug in FOP 2.0 as API changes are not documented to upgrade from FOP 1.x Java API to FOP 2.0!
> Now I just can search and try and experiment if I get our old code somehow running with all those undocumented API changes. Can you please state a migration documentation for all methods (method signatures) that don't exist anymore? We can't start coding all over again from scratch. Thank you very much!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)