R: Difference between cocoon: and file:// in map:part

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. Best regards, Luca Morandini [EMAIL PROTECTED] -Messaggio originale- Da: Piotr Legiecki

Re: R: Difference between cocoon: and file:// in map:part

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.xml

RE: R: Difference between cocoon: and file:// in map:part

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: Piotr, the cocoon: pseudo-protocol

R: R: Difference between cocoon: and file:// in map:part

novembre 2002 14.36 A: [EMAIL PROTECTED] Oggetto: Re: R: Difference between cocoon: and file:// in map:part 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

Re: R: Difference between cocoon: and file:// in map:part

Reinhard Poetz wrote: So the joined parts are not xml files anymore but html files? So I can't use map:transform src=styles/menuandbook2html.xsl/ on them anymore and I can't also use map:serialize/ You have to possiblities: 1. Each of the map:part-pipelines returns the xml in the form

RE: R: Difference between cocoon: and file:// in map:part

Piotr, Here I don't need to transform one xml to another one. I need html as output. 2. map:aggregate element=site map:part src=content/menu.xml/ map:part src=content/books.xml/ /map:aggregate map:transform