> > 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).
The problem is, that it should be possible to dynamically integrate new
portlets into the portal. However, Cocoon needs to know, how these new
portlets have to be processed (which filters, stylesheets, etc.). A portlet
must even have the possibility to deliver its own stylesheet.
I haven't looked into Cocoon2 very deeply yet, but I think that dynamically
modifying Cocoon's processing "rules" - which I understood are defined in
the sitemap - won't be easy...
ingo.
--
--------------------------------------------------------------
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]
