Neeme Praks wrote:
<snip>
> well, yes... I understood that we'll stick with the current way of
> handling this stuff until we can switch over to Cocoon2. Then hopefully
> we can use Avalon framework for different backend (Turbine) and frontend
> (Cocoon2) services
yup.
> and Jetspeed itself would also become a
> block/component in Avalon.
I am not sure if this is technically possible. Jetspeed is complex and
nebulous. I think that the parts would have to be Avalon. Avalon needs
to be cleaned up though.
> However, there are some hurdles on the way:
> Turbine services would need to become Avalon aware and Cocoon2 has to be
> reality ;-)
yup.
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
