You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Vadim Gritsenko <va...@verizon.net> on 2002/07/31 15:50:44 UTC
map:resource issue
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? ;-)
Anybody?
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: map:resource issue
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Christian Haul [mailto:haul@dvs1.informatik.tu-darmstadt.de]
>
> 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".
Ok. I found that on userdocs/concepts/sitemap.html resource described
as:
"
The <map:resource> element is used as a placeholder for pipelines that
are used several times inside the document
"
Won't then this be better:
"
The <map:resource> element is used to define pipelines fragments that
can be reused several times inside the sitemap.
...
<map:resource> pipeline fragment can contain any sitemap components and
can include other resources. After execution of the resource, complete
pipeline must be assembled, containing from a reader, or one generator,
zero or more transformer(s), and one serializer.
".
> 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.
:-/
I won't say I'm happy to hear about this kind of bugs...
Vadim
> Chris.
> --
> C h r i s t i a n H a u l
> haul@informatik.tu-darmstadt.de
> fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: map:resource issue
Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
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
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: map:resource issue
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Leigh Dodds [mailto:ldodds@ingenta.com]
>
> I've documented how they _currently_ work here:
>
> http://outerthought.net/wiki/Wiki.jsp?page=Resources
Looks nice; but one remark:
> Resource pipelines do not respond to requests directly,
> as they don't have a Matcher.
This is not correct: they can use matchers. May be it should be:
> Resource pipelines declared in the resources section of
> the sitemap and do not respond to requests directly.
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: map:resource issue
Posted by Leigh Dodds <ld...@ingenta.com>.
I've documented how they _currently_ work here:
http://outerthought.net/wiki/Wiki.jsp?page=Resources
--
Leigh Dodds
Weblog: http://weblogs.userland.com/eclectic
Home: http://www.ldodds.com
Current Project: http://outerthought.net/wiki/Wiki.jsp
"Pluralitas non est ponenda sine necessitate" -- William of Ockham
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: map:resource issue
Posted by Giacomo Pati <gi...@apache.org>.
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.
Giaocmo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org