Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3F22A857.30305@gmx.de>
Date: Sat, 26 Jul 2003 18:12:07 +0200
From: Joerg Heinicke <joerg.heinicke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: dev@cocoon.apache.org
CC: users@cocoon.apache.org
Subject: processing flow for <map:call resource=""/> (was: <map:serialize
 type="{1}"/>)
References: <1059175881.959.16.camel@dhcppc1> <3F21D1FC.2050700@gmx.de>
 <3F222E79.1080605@outerthought.org> <3F224628.8010907@gmx.de>
 <3F224F4C.9090004@outerthought.org> <3F2270B4.4090309@gmx.de>
 <3F2290E1.1080005@outerthought.org>
In-Reply-To: <3F2290E1.1080005@outerthought.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

(Moving this discussion to dev list because it implies an more or less 
important change - wanted or not.)

The problem: Does the processing return to a calling pipeline after 
<map:call resource=""/>?

The docu at 
http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html#Calling+resources 
and http://wiki.cocoondev.org/Wiki.jsp?page=Resources says no (to 
whatever reasons). But I saw Marc's example at 
http://wiki.cocoondev.org/Wiki.jsp?page=CleanerSiteMapsThroughResources 
and he tested it again and it worked, i.e. the processing flow *does* 
return to the calling pipeline.

Is this change implied? What were the pros and contras of this 
behaviour? I only know the old behaviour and, yes, the return makes the 
sitemap pipeline snippets more flexible. And who updates the docu ;-)

Can anybody say something about it?

Joerg

Marc Portier wrote:

>>>> Hmm, much of the code on this page is wrong or at least misleading:
>>>>
>>>> <map:resource name="generate-data-xml">
>>>>   <map:generate type="myCSVGenerator" 
>>>> src="http://csv-server.domain/getData"/>
>>>> </map:resource>
>>>>
>>>> <map:resource name="generate-data-svg">
>>>>   <map:call resource="generate-data-xml"/>
>>>>   <map:transform src="xsl/datafilter.xsl"/>
>>>>   <map:transform src="xsl/data2svg.xsl"/>
>>>> </map:resource>
>>>> A <map:call resource=""/> is a one way ticket. The processing does 
>>>> not return to the calling pipeline. Or do I miss anything?
>>>
>>> I think it does... (at least it did at the time of writing since I 
>>> tested the code out)
>>>
>>> resources are pieces of pipelines that take up roles
>>> see also the accompanied page at
>>> http://wiki.cocoondev.org/Wiki.jsp?page=ResourceNaming
>>
>> If that's true it must be more a bug than a feature I guess: 
> 
> It is true.
> 
> Just did a simple test (using cvs head) by wrapping a generator inside a 
> resource and replacing the <map:generate by the fresh map:call/@resource 
> in a particular pipe (followed by transformers  and serializer of course)
> 
> as for the documentation:
> 
>> http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html#Calling+resources. 
> 
> I've spent some time to figure out if the wording 'calls to a resource 
> never return' could be interpreted in any other way but I'ld have to 
> concede that the doco is not in sync with code reality here...
> 
> 
> Maybe the docos are still reflecting how the previous sitemap 
> implementation was handling things? Anyone out there aware of the 
> history of things? (I never tested this with anything else then the 
> treeprocessor)
> 
> In any case I think this behavior is generaly useful (as the wiki page 
> tries to argument) and not harmful in any way...
> 
> regards,
> -marc=