that sure is a poor answer.  you can search yur head off in the mailing 
list and know no more than you did before.

i believe the answer to the question is very complex and therefore very 
time consuming to answer - but, no answer is better than "go look in the 
mailing list"

You will probably need to spend quite a bit of time studying the various 
products to understand their uses and relationships.  But, here is a tiny 
summary from my studies:
Jetspeed uses Turbine and ECS
Turbine uses Velocity, therefore, Jetspeed uses Velocity (though JSP is 
also an option)
Cocoon is an alternative to Turbine/Velocity.
Cocoon is based on Avalon - none of the other products are based on Avalon 
(this will cause the  products to appear to be diametrically opposed)
I have not familiarized myself with Struts - can't comment (it appears to 
be a framework in "competition" with Turbine).
Don't forget that Turbine uses Torque for database activity.

each product has their strengths and weaknesses.

note that Avalon represents the "best of thinking" that i have come across.

my personal goal for my projects is to use Jetspeed (which includes all the 
underpinnings) combined with Cocoon for complex presentation events - the 
Pipeline component of Cocoon. i think i want Cocoon pipelines available in 
Jetspeed portals - this is where i am designing to - hopefully i don't fall 
flat on my face...

Ray

----------
From:   Paul Spencer[SMTP:[EMAIL PROTECTED]]
Reply To:       Jetspeed Users List
Sent:   Wednesday, December 12, 2001 4:55 PM
To:     Jetspeed Users List
Subject:        Re: What's the relationship between JetSpeed - Cocoon -..

This question has been asked and answered many times.
Search the mailing list, http://www.mail-archive.com.

Paul Spencer


Patrick Munis wrote:

> I am new to Jetspeed and most Jakarta software. What's the relationship
> between JetSpeed - Cocoon -Velocity- Turbine - Struts -ECS. Can they be
> used together in a project?For example, Can I use cocoon's  xsp in
> Jetspeed?  Are they competing technologies. I'll appreciate any
> explanations.
>
> thanks
> Patrick
>
>



--
To unsubscribe, e-mail: 
  <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: 
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to