Daniel Fagerstrom wrote:
Now, having said that, I'm completely aware about that the core still is
to complicated. IMO we need to take the consequences of our move to
Spring and try to remove as many Avalon dependencies as possible. The
ideal would be to remove all Avalon dependencies from core and just have
an optional back compatibility block that users that depend on Avalon
interfaces could use.
The current mix of Spring management and Avalon life cycles in the core
is just to complicated.
I think that this should be the main goal for Cocoon 2.3.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
