Fennell, Philip wrote: > Jason, > >> My guess is that Saxon 8.6 was actually performing the XInclude > inclusions, >> not the xinclude transformer, since as far as I know the transformer > doesn't >> have a concept of "source document location" and resolves relative > paths from >> the sitemap context. Perhaps something changed with Saxon 8.7.x so > that it >> no longer evaluates XIncludes, so now you're seeing the transformer in > action. > > Although you say that 'the xinclude transformer, since as far as I know > the transformer doesn't > have a concept of "source document location"' that doesn't explain why > both Xalan and Saxon 8.6.x > Where quite happy with paths relative to the source document (the > document being processed by Cocoon) > And only when Saxon 8.7.x is introduced does the context shift to the > Cocoon web application.
I thought we were just talking about Saxon here; now that you say Xalan behaves the same way that changes the picture and blows my theory out of the water. ;) So perhaps it's actually the other way around: Xalan and Saxon 8.6.x do not process XIncludes, whereas 8.7.x does but does not know how to properly determine the source document location? Just trying to find a pattern here. A way to test this would be to remove the xinclude transform step from your pipeline and see if the includes are still processed. > > A compliant XInclude processor, in the absence of an xml:base attribute, > should resolve URIs relative to the document in which the XInclude > instruction is encountered. > >> Perhaps you could handle both cases by using: >> <xi:include href="context:/content/resources/site/login.xml"> > > I try to avoid where possible using context, cocoon and resource > protocols as they tie the content to this application. > > As I cannot provide the whole source for the webapp I am working on I > will endevour to construct a simple test example webapp that illustrates > the problem. > > Thanks. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
