Raphael Luta wrote:
> 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...
Can't wait until then ;-)
I would think that a device negotiation layer as you could call Cocoon would
be extremely helpful working towards different devices - it does already
quite a lot of things in terms of user agent detection and the like.
> 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.
What do you mean with dynamic aggregation? User-based? From what I
understood of what Giacomo told me, the Action component is the way to go
for all things dynamic in Cocoon(2).
</Steven>
--
--------------------------------------------------------------
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]
