cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <vgritse...@hns.com>
Subject RE: XSPGenerator
Date Wed, 13 Dec 2000 16:22:24 GMT
> -----Original Message-----
> From: Giacomo Pati [mailto:pati_giacomo@yahoo.com]
> Sent: Wednesday, December 13, 2000 10:21
>
> --- Vadim Gritsenko <vgritsenko@hns.com> wrote:
> > I think this is an exellent idea!
> > I assume that <map:pipeline name="menu"> can have inner
> > <map:transform>
> > tags.
>
> I'm totally -1 on transforms in a aggregation definition because it
> would mix concerns. You should transform the aggregated content
> afterwards as Paul mentioned (see below).

It's a pity... Let's look at this example (syntax as in your previous
email):

<map:aggregate>
    <map:aggregation-part element="weather">
        <map:generate type="weather-source"/>
        <map:transform
src="stylesheets/weather-external-dtd-to-internal.xsl"/>
    </map:aggregation-part>
    <map:aggregation-part element="news">
        <map:generate type="news-source"/>
        <map:transform src="stylesheets/newsml-dtd-to-internal.xsl"/>
    </map:aggregation-part>
    ...
</map:aggregate>
<map:transform src="stylesheets/aggregate-to-layout.xsl"/>
<map:transform src="stylesheets/layout-to-html.xsl"/>
<map:serialize/>

You suggest to remove all transforms from <map:aggregation-part> and put it
after
<map:aggregate>. Do you think that this will be convinient/effective?

And, another question: In the tag
	<map:aggregation-part element="heading" internal="myapp/foo"/>
content is produced via sitemap recursivly ==> so, this can have some
transformations steps
already performed (before and not afterwards aggregation). OR - are you
going to disable transforms
in this situation?


>
> Giacomo
>
</snip>

Thanks,
Vadim


Mime
View raw message