I agree with most of your post but I would add one more use case for the
Cocoon Portal.
- Web sites which have a desire to incorporate portlets of various types
(JSR-168, WSRP, bridges, cocoon pipelines, etc) without looking like or
behaving like a portal.
As for what I am most interested in, all the portals will share some
commonality in that they all need to deploy portlets, they all require
security, they all want to provide personalization features, etc.
Ideally, many of these features could be extracted into a set of
frameworks that all the various portals could leverage. However, I
would expect that when integrated into Jetspeed the variety of choices
or set of features would be more extensive than with some of the other
portals.
I'm not really as interested in creating a "light portal" as I am in
sharing as much between the projects as possible. However, at
ApacheCon, the Geronimo team spoke about incorporating Pluto as its
admin console and perhaps into Geronimo itself. If this is done I think
it would make sense that if a Geronimo customer decided to use Jetspeed
instead that they would just get an enhanced portal - ideally, all of
Geronimo's documented procedures would still work.
Likewise, in Cocoon we would prefer to leverage a common code base than
go "borrowing" from other projects.
So what I would like to see is a "portal common" project rather than a
"portal light" project.
Ralph
Raphaël Luta wrote:
Cocoon Portal (not really Portals project but closely related)
-------------
Mission:
Provide a full-featured, reliable entreprise portal
Main Use Cases:
- Corporate intranet portals
- Internet portals
