Hi Felix, We have yet to merge J2 Cornerstone into J2. We hope to use Cornerstone for mass customization and JMX support. As IoC and components go, we have settled on using a combination of PicoConatiner for components and NanoContainer for assembling those PicoContainers using the groovy scripting language. Our eventual goal is to eliminate as many factories and static singletons as possible and make a sure all components are constructed at assembly time with all of there dependencies in place, i.e. no inconsistent objects.
Regards, *================================* | Scott T Weaver | | <[EMAIL PROTECTED]> | | Apache Jetspeed Portal Project | | Apache Pluto Portlet Container | *================================* > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Sunday, March 14, 2004 3:45 PM > To: [EMAIL PROTECTED] > Subject: [J2] Status Cornerstone & Avalon > > hi, > > can anybody provide me some informations about the cornerstone-framework > and his disposal in jetspeed2? > > i took a short look at the cornerstone-docs in j2 cvs and it seems, that > cornerstone fits nice in j2, because cornerstone will allow "mass > customization" - which sounds very helpful if you develop your own > portal-solutionn based upon j2 framework. > > but i don�t understand the difference between avalon and cornerstone. > both are component frameworks (?) and it sounds to me, that they are > having the same intention (meet the requirements for > framework-development, e.g.: low coupling between components, scalable > architecture, customize the framework, providing some tools and > utilities)? > > thanks in andvance, > felix > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
