Piotr,
> Here I don't need to transform one xml to another one. I need html as
> output.
>
> > 2.
> >
> >
> >
> >
> >
> >
> >
> > In this case you read your books and your menu directly (without using
> > sub-pipelines) and you only
Reinhard Poetz wrote:
So the joined parts are not xml files anymore but html files? So I
can't use
on them anymore and I can't also use
You have to possiblities:
1. Each of the map:part-pipelines returns the xml in the form you need it
for your client. But make sure to use the XML seria
Piotr,
> -Original Message-
> From: Piotr Legiecki [mailto:piotrlg@;sci.pam.szczecin.pl]
> Sent: Thursday, November 14, 2002 2:36 PM
> To: [EMAIL PROTECTED]
> Subject: Re: R: Difference between cocoon: and file:// in map:part
>
>
> Luca Morandini wrote:
> &
Luca Morandini wrote:
Piotr,
the "cocoon:" pseudo-protocol doesn't search for files, but for pipelines.
With this pseudo-protocol you can build pipelines and call them (more or
less as subroutines) from any aggregation.
I see. So when I want to separate navigation and content (having
menu.xm
