Stefano Mazzocchi <[EMAIL PROTECTED]> writes: > Hunsberger, Peter wrote: > > > Maybe I'm > > just too optimistic in believing there should be container > > implementations mature enough for Cocoon to depend on? > > What *really* bothers me about this thread is the fact that very few > seem to realize that "maturity" for dependencies means > "stability of the > contract and stability of the community". > > Avalon is dead. > > Excalibur is asleep. > > Spring is outside the ASF. > > Geronimo is still incubating. > > Can you see the pattern?
Umm, I don't really see a pattern here. From everything I've seen the communities involved with Spring and Geronimo have little in common with the Avalon/Excalibur communities. (Let me qualify that by saying I haven't looked that closely.) More-over, they both have the advantage of being able to look at past history and learn from it. > History should teach people not to repeat the same mistakes > again... but hey, what do I know, I've only been around here for 7 years. Many people have learned many things both technically and community wise in the past 7 years. If it is really this bad why aren't we writing our own XML parsers and XSLT engines? After all they are as critical to Cocoon as the containers. Why not take it all the way and write our own JVM?