cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: [RT] Another step to blocks: Application container support
Date Sat, 12 Mar 2005 13:21:30 GMT
Bertrand Delacretaz wrote:
> Le 11 mars 05, à 19:45, Carsten Ziegeler a écrit :
> IIUC the mechanism that you suggest would make it possible to support 
> new DCCs by creating some kind of adapter class for them? In this way 
> we could provide adapters for (say) Spring and Hivemind without closing 
> doors to other options.
Yes, exactly.

>>...b) Direct support for DCC. Using these frameworks is not that 
>>inside Cocoon, but I think it could be easier.
>>What do you think if e.g. a "getComponent("something")" in flow uses a
>>Spring BeanFactory (and if the factory does not have the bean/component
>>then the usual Avalon mechanism is used). The same would happen if you
>>get a service manager from the Cocoon core...
> Does that mean "chaining" containers, asking them in turn until one of 
> them finds the component? If this is implemented at the sitemap level, 
> would we then get a chain like this to get a component?
> -Ask this sitemap's DCC for the component
> -If not found, ask this sitemap's service manager
> -if not found, ask the parent sitemap, which asks its DCC then its 
> service manager, and so on
> Just asking to check my understanding.
Yes, that's the idea.


Carsten Ziegeler - Open Source Group, S&N AG

View raw message