cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz Kossakowski <>
Subject Re: Cocoon 2.2 - Cocoon Forms 1.0 block: Replacing Avalon's ServiceManager interface with Spring 2
Date Sun, 13 Apr 2008 19:10:57 GMT
Vadim Gritsenko pisze:
> On Apr 10, 2008, at 3:58 PM, Magnus Haraldsen Amundsen wrote:
>> I'm looking into the Cocoon Forms 1.0 block (with Cocoon 2.2) and it 
>> seems very nice. But I see that the Java API example at 
>> use 
>> Avalon's ServiceManager interface. However, at the "New in 2.2" page 
>> it says that "Cocoon 2.2 doesn't use an Avalon-based component manager 
>> any more but uses Spring 2 instead.".
> Cocoon 2.2 internally uses Spring, but it still provides backward 
> compatibility (as far as it's possible) with Cocoon 2.1, so it 
> implements Avalon functionality and provides an implementation of 
> Avalon's ServiceManager. Because of this CForms 1.0 can continue to use 
> ServiceManager.
> I should also mention that there is CForms version 1.1 which does not 
> use ServiceManager anymore and is migrated to Spring.
> Links to CForms 1.0 and 1.1:

I would add that we have already Spring implementation for Apples, see[1]. This way, Controllers
be just Spring beans so Dependency Injection can be used instead of ServletManager from Avalon.

Magnus, since you said you don't know Spring or Avalon I think you will have hard times using
code in Cocoon. I would say that you don't need to be a master of Spring to use Cocoon but
basics are highly recommended.

In this particular case I would advise you to take a look at apples block samples[2][3] and
out how to migrate them to Spring with help of people from this list. This way you would learn

basics and could contribute migrated samples to community so others could benefit.


Grzegorz Kossakowski

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message