[EMAIL PROTECTED] wrote:
>
> Same here since we would not be working on top of Turbine, but be using
> Cocoon2 instead. I'm not sure whether a application neutral Portal API would
> be a feasible thing, at least a common feature list should be possible.
>
I think an application neutral Portal API is possible but would certainly leave
a lot of responsabilities on the portlet developers, especially if we aim for
multi-device access. More on this when I have finished my Jetspeed 2 paper...
> Since thoughts on content aggregation are surfacing quite a lot on the
> Cocoon dev list, and Santiago has been talking with the Cocoon people during
> ApacheCon, I believe working across the two apps could be beneficial for
> both.
>
The Cocoon project will mainly work on *static* content aggregation so that
they can offer the same functionalities than Turbine layout model. A
Jetspeed implementation on Cocoon 2 will definitely take advantage of their
work in static aggregation but I don't see currently a way to integrate
in a meaningful way dynamic aggregation in a Cocoon 2 sitemap.
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
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]
