Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 86490 invoked from network); 15 Feb 2008 08:09:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Feb 2008 08:09:22 -0000 Received: (qmail 37690 invoked by uid 500); 15 Feb 2008 08:09:16 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 37646 invoked by uid 500); 15 Feb 2008 08:09:16 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 37635 invoked by uid 99); 15 Feb 2008 08:09:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Feb 2008 00:09:16 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [213.239.215.103] (HELO tux17.hoststar.ch) (213.239.215.103) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Feb 2008 08:08:42 +0000 Received: from [127.0.0.1] (adsl-89-217-29-172.adslplus.ch [89.217.29.172]) (authenticated bits=0) by tux17.hoststar.ch (8.13.6/8.12.11) with ESMTP id m1F88nFq017829 for ; Fri, 15 Feb 2008 09:08:50 +0100 Date: Fri, 15 Feb 2008 09:09:28 +0100 From: Jeremias Maerki To: dev@forrest.apache.org Subject: Re: Problem with fop94 locating an aart-image In-Reply-To: <1203022445.6077.39.camel@cartman> References: <1203019697.6077.29.camel@cartman> <1203022445.6077.39.camel@cartman> Message-Id: <20080215090725.AEA0.DEV@jeremias-maerki.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Mailer: Becky! ver. 2.28.01 [en] X-Antivirus: avast! (VPS 080214-0, 14.02.2008), Outbound message X-Antivirus-Status: Clean X-Virus-Checked: Checked by ClamAV on apache.org Please also note that the fop-ng block provides a URIResolver to FOP. So special URI schemes should now work inside FO documents. Not sure if it helps in this case but I have a feeling it would. On 14.02.2008 21:54:05 Thorsten Scherler wrote: > On Thu, 2008-02-14 at 21:08 +0100, Thorsten Scherler wrote: > ... > >=20 > > My prior hack to did not work because i= t > > seems the resulting document is ignoring the servlet context and use th= e > > relative path from himself.=20 >=20 > But http://www.thescripts.com/forum/thread84856.html gives the > impression that it should work. >=20 > Fueled by http://marc.info/?l=3Dfop-dev&m=3D100719308626996&w=3D2 > "If you want a relative URI, why not just use a relative URI? I.e.,=20 > src=3D"config/isappdev/applications/RVWebApp1/WEB-INF/lib/ClinTrialLogoGr= eenBig.gif"?=20 > Then the current protocol, host, and directory will be used as the base U= RI=20 > and the relative URI interpreted relative to that." >=20 > http://xmlgraphics.apache.org/fop/fo.html#external-resources > "URIs may be either absolute or relative to a base URI.=20 > (See FOP: Configuration for information on setting the base=20 > URI for a FOP session). Here is an example referencing=20 > an external-graphic that is relative to the base URI: > " > " >=20 > If you use the url() then I get "Could not find function: url" since > this in not a standard xsl 1 function. >=20 > >=20 > > The problem as I understand it is that=20 > > needs an absolute url to > > resolve the image.=20 >=20 > http://www.nabble.com/Help!-URI-for-fo:external-graphic-in-web-service-td= 14657418.html >=20 > "XSL-FO prescribes that only a=20 > URI is allowed. To go from a filepath to a URI you should rewrite it=20 > something like "file:///c:/project/scr/certificate.gif" (note the=20 > forward slashes!)." >=20 > Our image does not exist in the file system, only via http://=20 >=20 > salu2 > --=20 > Thorsten Scherler thorsten.at.apache.org > Open Source Java consulting, training and solutions Jeremias Maerki