> document's location
I thought that too, which made me ask the question in the first place.
I followed your link to bugzilla but could not see the relevance.
Either something has been added to or taken away from Saxon that is changing the way the XInclude transform is working. After all, I have have not changed Cocoon since mid to late last year (2005) and the problem only appeared this week when we replaced the previous saxon8.6 jars in $TOMCAT_HOME/webapps/cocoon/WEB-INF/lib with the 8.7.1 jars.
On 09/05/06, Frans Englich <
[EMAIL PROTECTED]> wrote:
On Tuesday 09 May 2006 11:02, Philip Fennell wrote:
> I was previously using Saxon 8.6 as the default XSLT processor and I make
> use of the XInclude transformer as follows:
[...]
> Now in this example the xinclude's @href is resolved relative to the source
> documents location. However, if I replace Saxon 8.6 with Saxon
> 8.7.1 (I don't know if the '.1' makes a difference) the @href gets resolved
> relative to the webapp context.
If I recall correctly, it is correct to resolve against the source document's
location, unless one is not standards conformant.
This might be of relevance:
http://issues.apache.org/bugzilla/show_bug.cgi?id=31600
Cheers,
Frans
--
Regards
Philip Fennell
