ocument?"
Con
> -Original Message-
> From: icewind [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 10 July 2002 11:41
> To: [EMAIL PROTECTED]
> Subject: RE: generating a manifest of xml docs
>
>
>
>
> Conal,
>
> Thank you very much for taking the time
Conal,
Thank you very much for taking the time to explain
your setup to me. I have found it to be very valuable
and I think others on the list will too.
I got it working on my setup by including the full
XPath expression for the node I want to select in the
xinclude tag. I's a little uncertain
> -Original Message-
> From: icewind [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 9 July 2002 03:26
> To: [EMAIL PROTECTED]
> Subject: generating a manifest of xml docs
>
>
> I would like to be able to have cocoon take an entire
> directory of xml files, go through it, grab the
> contents o
Another way is to access the files via document() and the cocoon or
context protocol. The first one goes back the sitemap again and should
solve the cache problem too. The second one is only a common directory
base (root sitemap directory), but mostly the '/', Joerg suggested, is
the better so
icewind wrote:
> I tried this but I ran into a problem. The output of
> the DirectoryGenerator only gives the filename, not
> the full path. When the stylesheet, which is in
> another directory attempts to open the file, it cannot
> because no XML files in the directory where the
> stylesheet live
I tried this but I ran into a problem. The output of
the DirectoryGenerator only gives the filename, not
the full path. When the stylesheet, which is in
another directory attempts to open the file, it cannot
because no XML files in the directory where the
stylesheet lives. Any suggestions?
> 1
1. use the DirectoryGenerator as startpoint
2. use XSLT to transform the resulting XML to your wanted output, e.g. using
document() to get the content of the specific tag
Regards,
Joerg
icewind wrote:
> I would like to be able to have cocoon take an entire
> directory of xml files, go through
