cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject Re: application-context loading order
Date Fri, 14 Mar 2008 08:18:28 GMT
On 14.03.2008 04:14, Reinhard Poetz wrote:

>>> Could somebody please explain in wich order springs application 
>>> context is created (out of all 'block-specific' contexts inside 
>>> META-INF/cocoon/spring/*.xml).
>>
>> I don't think the order of the block's spring.xml matter since AFAIK a 
>> child context is created for every block extending a common parent 
>> context. So inside a block you only have access to the block's beans 
>> and the one from the parent context.
> 
> that's not correct: All bean declared in META-INF/cocoon/spring/*.xml 
> are loaded into the global application context. The files are ordered 
> alphabetically.
> 
> There also exist *sitemap* local beans which are only available from 
> within a particular sitemap.

Ok, thanks for correcting. Just to rephrase it: Beans declared in the 
sitemap (Or what does "sitemap local beans" mean? Are they Avalon 
components?) are in a block-specific child context, but beans declared 
in the block's spring.xml are not? How to extend blocks then?

Joerg

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


Mime
View raw message