On 31.Jul.2002 -- 09:50 AM, 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.
Yes, I've written that paragraph. It is a simplification that I
thought would be OK when introducing sitemap components.
> 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.
Right, that's the behaviour that resources always exhibited. So that
is "correct".
On a side note: treeprocessor has a "bug" that resources return to the
calling place if they don't have a serializer. There has been some
discussion around that feature. AFAIR it was to be cosidered and
should not be advertised nor removed. Many were in favour of keeping
it.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
