cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15316] - FOP does not resolve relative paths
Date Mon, 11 Oct 2004 09:15:57 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=15316>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=15316

FOP does not resolve relative paths

Alfred.Nathaniel@swx.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |ASSIGNED



------- Additional Comments From Alfred.Nathaniel@swx.com  2004-10-11 09:15 -------
I'm looking at this at the Ghent Hackathon.

Ideally, we should pass to FOP the Cocoon source resolver in order to allow 
inclusion of images generated from Cocoon pipelines.  Unfortunately, FOP does 
not provide this interface right now.

FOP allows in fo:external-graphic/@src absolute file paths and http URLs.

Therefor we can solve two important use cases in Cocoon.  Relative file paths 
can be transformed to absolute paths with a well-defined base directory 
(location of sitemap file).  cocoon:/ URIs can be transformed to http: URLs 
with the base passed as configuration parameter.

All we need to do is to intercept fo:external-graphic in 
FOPSerializer.startElement and patch the src attribute.

Mime
View raw message