Re: Recursive XInclude

[Michael Wechner]

Thanks a lot for your help Vadim. That's the way it worked:

<xi:include xml:base="http://slashdot.org" href="/slashdot.xml"/>
<xi:include xml:base="cocoon:" href="/live/sections/al/section.xml#xpointer(/section/article[1])"/>

But having the "cocoon" protocol in there to be able to resolve xi:iclude recursively isn't very nice.

All the best

Michael





Vadim Gritsenko wrote:

00d701c1a476$3743c910$90a4558b@vgritsenkopc">

From: Michael Wechner [mailto:[EMAIL PROTECTED]] 

Thanks Vadim, but the XInclude Transformer does not interpret cocoon:
as a protocol, but rather as a filesystem path. I have the same problem
with
<xi:include href=""http://slashdot.org/slashdot.xml"/>

It says: Resource can't be found.

I remember there was a thread in the mailing list about something like
that, but I can't
find it anymore.

Sorry for asking the same things again.
<<<

It was sad on the list:

---------------------
There is a bug/feature in the XInclude transformer which assumes that
unless a base attribute is specified somewhere, the <xi:include/>'s href
value is a filename, and prepends the Cocoon install path in front of
it.  This is probably turning your
 "http://slashdot.org/" into
"/usr/local/tomcat/webapps/Cocoon/http://slashdot...".  The solution is
to add a base="http://slashdot.org" attribute either at (I believe) or
above (for sure) the <xi:include/> element. Then just use the document
portion of the desired URL for the <xi:include/>'s href attribute
(href="/slashdot.xml").
--------------------

Try this base attribute with cocoon: protocol, it should work.

Vadim


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mai
l: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>