cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reinhard Poetz" <reinhard_po...@gmx.net>
Subject RE: R: Difference between cocoon: and file:// in map:part
Date Thu, 14 Nov 2002 14:59:36 GMT
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 src="styles/menuandbook2html.xsl"/>
> >          <map:serialize type="html"/>
> >
> > In this case you read your books and your menu directly (without using
> > sub-pipelines) and you only have one stylesheets that
> transforms your xml in
> > html.
>
> And this is what I don't want (ie one big xsl). I want one xsl for menu
> (and generally navigation) and one for content, so I will have a few
> small xsl files vs one big (easier to manage).
>
> So I think the second step is the way to go and manage xsl files using
> one 'main' (here menuandbook2html.xsl) xsl which includes the rest.

Yes, you can use includes within your stylesheet or you call in map:part
sub-pipelines which already return html (of course in xml).

I would prefer one stylesheet with includes.

Regards,
Reinhard

>
> Sounds reasonably?
>
> Thanx
> Piotr Legiecki



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

To unsubscribe, e-mail:     <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>


Mime
View raw message