cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: map:resource issue
Date Mon, 12 Aug 2002 10:12:29 GMT
On Wed, 31 Jul 2002, Vadim Gritsenko wrote:

> Hi all,
> As pointed out by Lorenzo De Sio on user group (Subj: Multiple
> map:resource calls), there is an issue with map:resource handling.
> On one side, sitemap.xmap states:
> <!--
>   Resources are pipeline fragments that may be used from different
>   pipeline fragments. For our needs, they behave exactly like
>   pipelines, only that they are not accessible from outside.
>   Hence I will explain what's inside below for pipelines.
> -->
> On the other, implementation of the sitemap stops processing right after
> call to resource, which means that resource is not fragment at all, but
> more similar to a view, which must be placed at the end of pipeline. In
> my understanding of word "fragment", fragment can be used in the middle
> of pipeline - which is not possible right now.
> Who knows/remembers how resources *should* work?
> Old timer Giacomo? ;-)

A resource was meant to be a macro-like predefined complete pipeline which
can be used (called) from different points in the sitemap. You're right
saying that a resource is itself a complete pipeline and not a fragment
which gets included into a already partially assebled pipeline.
Admittedly the semantic verb "call" in resource activation is leading to
wrong interpretation of it.


To unsubscribe, e-mail:
For additional commands, email:

View raw message