cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject RequestLifecycle [was: Re: cvs commit: xml-cocoon2/src/java/org/apache/cocoon/sitemap DefaultSitemapComponentSelector.java]
Date Thu, 07 Feb 2002 20:18:28 GMT
Carsten Ziegeler wrote:

>Sylvain Wallez wrote:
>
>><snipped>
>>
>>
>>But I have also have a question : should enter/leaveEnvironment be
>>called only once per request (i.e. on the root sitemap), or also on
>>every nested subsitemap ?
>>
>>In sitemap.handler, it seems to be called for each subsitemap, which
>>means for example that a RequestLifecycle component looked up in the
>>main sitemap is hidden when we enter in a subsitemap. Is this the
>>intended behaviour ?
>>
>Argh, no of course not - the intended behaviour is that a RequestLifecycle
>component is valid for a request regardless in what sitemap it is looked up.
>But, if an internal request is process (using the cocoon: protocol),
>the RequestLifecycle component of the calling process are not valid inside
>the internal request. That is the intention of the lines in the
>sitemap.handler.
>
>Well, lets see if I can fix it somehow. Thanks for reporting it!
>
>Carsten
>
One more detail : should a "cocoon:" URL considered as a new request, or 
should it inherit RequestLifecycle components of the calling request ?

I would say it should be considered as a new request, in order to behave 
independently of the calling environment, but what do you think ?

Sylvain

-- 
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message