I am using xsl:include in 2.1dev (from about 12/7) and haven't seen the
problem you're reporting.

Geoff

> -----Original Message-----
> From: Niclas Hedhman [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 13, 2003 11:54 PM
> To: [EMAIL PROTECTED]
> Subject: Re: xsl:include's root is in Tomcat's root.
>
>
>
> If the href starts with "cocoon" the href is relative to the including
> stylesheet, otherwise it is relative to "tomcat/webapps".
> EXCEPT, if I write "cocoon/../" then we have relative to "tomcat/webapps"
> again.
>
> This can't possibly be correct.
>
> Is this some side-effect of sitemap settings? Using the default
> sitemap (from
> binary download) with the following added section;
>
>    <map:match pattern="products/*/datasheets/*">
>     <map:generate src="products/{1}/datasheets/{2}"/>
>     <map:transform src="products/{1}/datasheets/style/datasheet.xsl"/>
>     <map:serialize type="xhtml" />
>    </map:match>
>
>
>
> Niclas
>
> On Tuesday 14 January 2003 12:31, Niclas Hedhman wrote:
> > I have a
> >
> > <xsl:include href="features.xsl" />
> >
> > in the main XSL stylesheet, and I get the error message;
> >
> > java.io.FileNotFoundException:
> >
> /home/niclas/internus/bali/cocoon/jakarta-tomcat-4.0.3/connections.xsl (No
> > such file or directory)
> >
> > which I think is way off.
> > Is this expected behaviour or have I completely fouled up the
> installation?
> >
> > Shouldn't all <xsl:include> be relative the same directory as
> the including
> > stylesheet is in, if no initial "/" is given?
> >
> >
> > Niclas
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to