: [EMAIL PROTECTED]
Subject: Re: Recursive XInclude
Thanks a lot for your help
Vadim. That's the way it worked:
xml:base="http://slashdot.org"
href=""/slashdot.xml"/>
xml:base="cocoon:"
href=""/live/sections/al/section.xml#xpointer(/section/arti
Thanks a lot for your help Vadim. That's the way it worked:
xml:base="http://slashdot.org" href="/slashdot.xml"/>
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
>>>
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
http://slashdot.org/slashdot.xml"/>
It says: Resource can't be found.
I remember there was a t
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
"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,
> From: Michael Wechner [mailto:[EMAIL PROTECTED]]
>
> Hi
>
> Does anybody know if the XInclude Transformer is actually resolving
the
> "xi:include" recursively?
No.
> I tried something like that:
>
> department.xml:
> xi:include href="group.xml"
>
> group.xml:
> xi:include href="member.
Hi
Does anybody know if the XInclude Transformer is actually resolving the
"xi:include"
recursively?
I tried something like that:
department.xml:
xi:include href="group.xml"
group.xml:
xi:include href="member.xml"
member.xml:
Michael
and got the following result:
department.xml:
x
