Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: pass (nike.apache.org: domain of
 thorsten.scherler.ext@juntadeandalucia.es designates 217.12.18.114 as
 permitted sender)
Subject: Re: Problem with fop94 locating an aart-image
From: Thorsten Scherler <thorsten.scherler.ext@juntadeandalucia.es>
To: dev@forrest.apache.org
In-Reply-To: <20080215090725.AEA0.DEV@jeremias-maerki.ch>
References: <1203019697.6077.29.camel@cartman>
	 <1203022445.6077.39.camel@cartman>
	 <20080215090725.AEA0.DEV@jeremias-maerki.ch>
Content-Type: text/plain
Date: Fri, 15 Feb 2008 11:25:16 +0100
Message-Id: <1203071116.5827.44.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Fri, 2008-02-15 at 09:09 +0100, Jeremias Maerki wrote:
> 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.

You mean something like href="cocoon://..." also would work?

salu2

> 
> On 14.02.2008 21:54:05 Thorsten Scherler wrote:
> > On Thu, 2008-02-14 at 21:08 +0100, Thorsten Scherler wrote:
> > ...
> > > 
> > > My prior hack to <xsl:value-of select="@src"/> did not work because it
> > > seems the resulting document is ignoring the servlet context and use the
> > > relative path from himself. 
> > 
> > But http://www.thescripts.com/forum/thread84856.html gives the
> > impression that it should work.
> > 
> > Fueled by http://marc.info/?l=fop-dev&m=100719308626996&w=2
> > "If you want a relative URI, why not just use a relative URI?  I.e., 
> > src="config/isappdev/applications/RVWebApp1/WEB-INF/lib/ClinTrialLogoGreenBig.gif"? 
> > Then the current protocol, host, and directory will be used as the base URI 
> > and the relative URI interpreted relative to that."
> > 
> > http://xmlgraphics.apache.org/fop/fo.html#external-resources
> > "URIs may be either absolute or relative to a base URI. 
> > (See FOP: Configuration for information on setting the base 
> > URI for a FOP session). Here is an example referencing 
> > an external-graphic that is relative to the base URI:
> > <fo:external-graphic src="url('images/logo.jpg')"/>"
> > "
> > 
> > If you use the url() then I get "Could not find function: url" since
> > this in not a standard xsl 1 function.
> > 
> > > 
> > > The problem as I understand it is that 
> > > <fo:external-graphic src="$absoluteUrl"/> needs an absolute url to
> > > resolve the image. 
> > 
> > http://www.nabble.com/Help!-URI-for-fo:external-graphic-in-web-service-td14657418.html
> > 
> > "XSL-FO prescribes that only a 
> > URI is allowed. To go from a filepath to a URI you should rewrite it 
> > something like "file:///c:/project/scr/certificate.gif" (note the 
> > forward slashes!)."
> > 
> > Our image does not exist in the file system, only via http:// 
> > 
> > salu2
> > -- 
> > Thorsten Scherler                                 thorsten.at.apache.org
> > Open Source Java                      consulting, training and solutions
> 
> 
> 
> 
> Jeremias Maerki
> 
-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions