Carsten Ziegeler wrote:
Yes, agreed - there are several issues here discussed at once. I'll
comment on some of them :)
Cocoon Portal is currently part of Cocoon (obviously :) ). Now, it
really lacks of committers and visibility. Noone knows that Cocoon has a
nice portal solution. Ralph and myself are nearly the only developers on
the portal. Now what do you guys think of moving the Cocoon portal to
the portals project to create more visibility and hopefully to make
collaboration between the various portals projects more efficient?
Carsten and I disagree on whether this is a good idea. The cocoon portal
relies on Cocoon constructs and at this point it cannot be used without
the Cocoon framework. So it feels a little wierd to me to move it to
the portals project. However, it is just another Cocoon block and so it
can move to any part of the svn repository. But I'm not sure that
simply moving it to Portals will attract new committers to it.
Now, although I wrote more than 90% of the Cocoon portal code (and this
fact shows the community problem of the portal), I don't care what
happens with it over the long term. I think, in the end we should try to
have only one portal solution at Apache - being this Jetspeed 2, Cocoon
or something different is imho not that important. Now, I don't know J2
that much, but from what I understand so far, it seems similar to the
Cocoon solution in most areas, so I might be possible to add some things
from the Cocoon portal to J2 and then ditch the Cocoon code (I guess
this now scares Ralph :) ) - But I see this more as a long term goal
which we can start addressing when I know more about J2 - I'm, planning
to look into J2 in the next weeks and then see, if it's possible to add
some ideas from Cocoon there. I'll start a thread at the J2 list by then.
Wow. It is rare that Carsten and I disagree on something.
Carsten is absolutely right that this idea scares me. While some parts
of the Cocoon portal should and could be the same as Jetspeed, I simply
don't see how it could replace Cocoon's portal. Cocoon as a whole uses
pipelines and source resolvers to leverage XML and XSLT. The Cocoon
portal does the same thing but at the portlet level. Furthermore, the
Portal allows Cocoon pipelines to be used as portlets and it uses
pipelines to obtain all of its configuration. Now, if the J2 portal can
be used and Cocoon just plugs in to the appropriate places to accomplish
the same thing then that would be fine. But I'm not sure that that is
possible which is why I'm suggesting looking for common components instead.
Ralph
