Re: xsl:include, xalan 2.1.0

[Marcus Crafter <cr...@fztig938.bank.dresdner.net>]

Hi All,

	Sorry, false alarm. After looking into the cocoon code a bit more I
	noticed this is a cocoon issue. I was a bit too trigger happy there.

	Cheers,

	Marcus

On Wed, 30 May 2001, Marcus Crafter wrote:

> Hi All,
> 
> 	I just updated my cocoon 2 source code, and have noticed some
> 	interesting behaviour (the updated code moves from Xalan 2.0.1 to
> 	2.1.0).
> 
> 	It's to do with xsl:include. Hope this doesn't read too confusing! :-)
> 
> 	In our project we have several files that are used by many others.
> 
> 	To make things easier we created a single meta-include file, which
> 	included all other required include files via relative paths, and we
> 	included that file in our stylesheets instead of naming the individual
> 	files themselves.
> 
> 	We also saw the benefit that, when specifying the 'meta-include' file
> 	relatively, it would still be able to find sub-included files, even if
> 	these sub-included files were included relatively within the
> 	meta-include file, as described above.
> 
> 	Xalan would use the meta-include file's path to resolv relative
> 	sub-include paths and not that of the calling stylesheet.
> 
> 	This behaviour seems to have changed in Xalan 2.1 ?
> 
> 	For example - meta-include file (includes.xsl) contains:
> 
> 		<xsl:include href="../js/ss1.xsl"/>
> 		<xsl:include href="../js/ss2.xsl"/>
> 
> 	and is referenced in another stylesheet like:
> 
> 		<xsl:include href="common/includes.xsl"/>
> 
> 	from the directory a/b/c
> 
> 	Xalan 2.0.1 read ss1.xsl/ss2.xsl like:
> 
> 		a/b/c/js/ss1.xsl and a/b/c/js/ss2.xsl
> 
> 	Xalan 2.1.0 reads ssl1.xsl/ss2.xsl like:
> 
> 		a/b/js/ss1.xsl and a/b/js/ss2.xsl
> 
> 	Which behaviour is right ?
> 	
> 	(ie. resolving included file paths from the main include file's path, or
> 	resolving included file paths from the file including the 'main
> 	include file').
> 
> 	Or have I lost the plot all together ?? :-)
> 
> 	Cheers,
> 
> 	Marcus
> 

-- 
        .....
     ,,$$$$$$$$$,      Marcus Crafter
    ;$'      '$$$$:    Computer Systems Engineer
    $:         $$$$:   Open Software Associates GmbH
     $       o_)$$$:   82-84 Mainzer Landstrasse
     ;$,    _/\ &&:'   60327 Frankfurt Germany
       '     /( &&&
           \_&&&&'     Email : Marcus.Crafter@osa.de
          &&&&.        Business Hours : +49 69 9757 200
    &&&&&&&:           After Hours    : +49 69 49086750