cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leszek Gawron <lgaw...@mobilebox.pl>
Subject Re: Bean overriding.
Date Tue, 09 Jan 2007 14:50:42 GMT
Carsten Ziegeler wrote:
> Leszek Gawron wrote:
>> One would like to provide a totally new implementation of core component
>> (i.e. store, continuations manager etc.). The current version of the
>> component will be loaded anyways (the bean definition resides somewhere
>> in cocoon-core.jar/META-INF/cocoon/spring/*.xml). Defining a new bean of
>> the same name will throw a nasty exception. What should the user do?
>>
> As far as I know, you'll not get an exception and the last definition is
> used.

What is the 100% reliable way to make the definition I want the last one?

-- 
Leszek Gawron                                    CTO at MobileBox Ltd.

Mime
View raw message