[ 
https://issues.apache.org/jira/browse/FOP-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johan Persson resolved FOP-2523.
--------------------------------
    Resolution: Invalid

The solution to fix the changed behavior of fop 2.x is to make sure there is a 
correct configuration file. It seems that fop 1.0 had different default values 
for the "base" URI in case no configuration was found.

To solve this problem one only has to setup a minimum fop configuration file as:
<fop version="1.0">
<!-- Base URL for resolving relative URLs -->
<base>./</base>
</fop>

and the run fop with the "-c" option to specify this config file unless one 
puts it in one of the default location where fop looks for it.

Will close this issue as it is not an issue (perhaps it should be mentioned in 
some "gotchas" when moving from fop 1.1 to fop 2.x)


> Behavior change in include path handling breaks existing 1.1 docs
> -----------------------------------------------------------------
>
>                 Key: FOP-2523
>                 URL: https://issues.apache.org/jira/browse/FOP-2523
>             Project: FOP
>          Issue Type: Bug
>          Components: image/jpeg, image/png
>    Affects Versions: 2.0
>         Environment: OS X , Linux
>            Reporter: Johan Persson
>            Priority: Minor
>              Labels: path
>
> When transforming a document with included files (images) there is a 
> different behavior between 1.1 and 2.x.
> Transformation that works with fop 1.1 no longer works with 2.0
> I suspect that this is not so much a bug as a change that breaks existing 
> build schemas due to fop making different assumption on relative paths in 1.1 
> compared with 2.x. but I have to yet figure out what the assumption is.
> If the generated .fo includes say, 
> {{<fo:external-graphics src="url(myimage.jpg) width="100%" height="auto">}}
> If all files (both images and .fo) are in a flat directory this works well 
> with 1.1. Running the same source through 2.0 will generate an error saying 
> that FOP cannot find the referred file (myimage.jpg)
> I suspect this is a common enough pattern to warrant some notice on how to 
> handle this situation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to