Title: RE: Integration of Cocoon and Jetspeed; is Turbine a liability?

> Well, I could take this question: we ARE building our ENTIRE portal on
> Jetspeed and I find it entirely possible... Now looking back to it,
> maybe we would have been better off by using just Cocoon (as currently
> we are not using syndication capabilities of Jetspeed very much, more
> the layout side of Jetspeed), but we are too far now... and the
> syndication capabilities might become handy later on...

I think this is the way we will go here. Have you found Jetspeed to
be a problem in any way? I'm asking because you said "maybe we would
have been better off by using just Cocoon", and I want to make sure
whether this means "Jetspeed was not really necessary, but it doesn't
hurt at all", or "Jetspeed has problems, and we should have used
Cocoon alone".

Also, would you happen to have a functional site I could visit, or,
even better, working source code... 8-) ? I'm still trying to understand
all the pieces in Jetspeed, and have not been able to find, for
example, where the layout is managed.

> However, I very much look forward to Cocoon2 and Jetspeed2, to build a
> "perfect" portal building framework... ;-)

Me too, from what I have been reading...

> Neeme

Thanks in advance,


--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
If this mail is in HTML format, blame Exchange Server: Q222508

Reply via email to