DO NOT REPLY [Bug 25272] New: - FNF thrown formatting test/resources/fop/image/align.fo

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25272>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25272

FNF thrown formatting test/resources/fop/image/align.fo

           Summary: FNF thrown formatting test/resources/fop/image/align.fo
           Product: Fop
           Version: 0.15
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: general
        AssignedTo: fop-dev@xml.apache.org
        ReportedBy: john@integerservices.no-ip.com


Running the following command from the 'root' directory of Fop 1.0dev throws
a FileNotFoundException. (The directory containing 'build.xml' and 'build.sh'.)

Reason: Fop does not use the directory of the foFile or foURL as the base 
directory for external files. 

For example:

<fo:external-graphic width="100pt" height="100pt" content-width="50pt"
content-height="50pt" src="file:logo.jpg"/>


java -Xms100m -Xmx200m -cp
.:build/fop.jar:lib/avalon-framework-4.1.4.jar:lib/batik.jar:lib/commons-io-dev-20030703.jar
org.apache.fop.apps.Fop -fo test/resources/fop/image/align.fo -pdf /tmp/17350.pdf
[INFO] 1.0dev
[ERROR] Error while opening stream for (file:logo.jpg): .logo.jpg (No such file
or directory)
java.io.FileNotFoundException: .logo.jpg (No such file or directory)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:106)
        at java.io.FileInputStream.<init>(FileInputStream.java:66)

Notes:

This problem was found running org.apache.fop.apps.Fop but should also be
present for programs running embedded Fop. 

A File or URL is passed to FOFileHandler which encapsulates an InputSource for 
SAX. The base directory needs to be remembered somewhere in the FOFileHandler 
and clients need to find it when they wish to access external files.

I'm not quite ready to offer up a patch for this because I don't have the full 
design history of this.