cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject Sub-sitemaps (was: Changes to the deployer plugin wrt shielded classloading)
Date Sat, 18 Nov 2006 20:20:43 GMT
On 18.11.2006 21:12, Mark Lundquist wrote:
> 
> On Nov 18, 2006, at 5:46 AM, Carsten Ziegeler wrote:
> 
>> So if you have two sitemaps in your block, one for /myblock and one for
>> /myblock/misc, then you add two component definitions to the spring
>> context and you don't have to mount the misc sub sitemap in the myblock
>> sitemap.
> 
> One aspect of sub-sitemaps, of course, is that they inherit component 
> definitions from upward in the hierarchy... does something like that 
> still work in the new model?

Component inheritance is a standard functionality of Spring's 
ApplicationContext implementations. So this should be no problem at all.

But I wonder if there is a replacement for "fallback to parent sitemap 
if no match was found in sub sitemap".

Jörg

Mime
View raw message