You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by "mail@felixguntrum.de" <ma...@felixguntrum.de> on 2004/03/14 21:44:59 UTC
[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: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: [J2] Status Cornerstone & Avalon
Posted by Paul Spencer <pa...@mindspring.com>.
Jan,
Please post you question to ONE list.
Paul Spencer
Jun Yang wrote:
> Felix,
>
> Scott already gave a good summary of how Cornerstone is used in J2. As
> far as how it compares with Avalon, I am not familiar with it enough to
> say anything interesting. What I can say is Cornerstone was is to
> alleviate the biggest pain we have seen in many previous projects:
> customization. It is very young still and we still have a lot to figure
> out (e.g. I need to figure out how Cornerstone can help in customizing
> Pico components wired using Groovy in J2).
>
> Jun
>
> mail@felixguntrum.de wrote:
>
>> 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: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [J2] Status Cornerstone & Avalon
Posted by Jun Yang <ju...@cisco.com>.
Felix,
Scott already gave a good summary of how Cornerstone is used in J2. As
far as how it compares with Avalon, I am not familiar with it enough to
say anything interesting. What I can say is Cornerstone was is to
alleviate the biggest pain we have seen in many previous projects:
customization. It is very young still and we still have a lot to figure
out (e.g. I need to figure out how Cornerstone can help in customizing
Pico components wired using Groovy in J2).
Jun
mail@felixguntrum.de wrote:
> 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: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: [J2] Status Cornerstone & Avalon
Posted by Jun Yang <ju...@cisco.com>.
Felix,
Scott already gave a good summary of how Cornerstone is used in J2. As
far as how it compares with Avalon, I am not familiar with it enough to
say anything interesting. What I can say is Cornerstone was is to
alleviate the biggest pain we have seen in many previous projects:
customization. It is very young still and we still have a lot to figure
out (e.g. I need to figure out how Cornerstone can help in customizing
Pico components wired using Groovy in J2).
Jun
mail@felixguntrum.de wrote:
> 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: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org