Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <dev@cocoon.apache.org>
Subject: RE: Portal Path
Date: Mon, 2 Aug 2004 13:11:53 +0200
Organization: S&N AG
MIME-Version: 1.0
In-Reply-To: <BAY19-F7XDMmkepSmSO00064c66@hotmail.com>
Thread-Index: AcR4eXHel60TZL1AStKSGf3gv5KbWQABY2kw
Message-ID: <OF54E7899F.8472BF39-ONC1256EE4.003CC735@sundn.de>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"

Jennifer Yip wrote:
> 
> Is it possible to get a quick outline of where the 
> development team are heading with Portal Blocks?
> 
As far as I know there are no new things planned for the portal.
The current version is running nicely and is used for several
websites already.
I could imagine that over time support for WSRP will be added,
but I'm not aware of anyone actually doing this.

> The new portal block does not appear to have any aspects for 
> managing Coplets and or users?
Currently you have to do this manually which means editing the
files using an editor. Tools are really missing and it would
be great if someone could develop something :)

> Is this likely to happen over next couple of months (or did I 
> miss something)?
I heard from several parties that they are interested in/trying
to build some tools and I guess that we will see some tools
in the next months, yes.

> 
> JetSpeed2 seems like a key aspect in the open source portal 
> world 
I think it will definitly play a role when a first version is released.

> and I read somewhere that JetSpeed2 was based on 
> Cocoon2 (I am going to try and look closer at this today) Is it?
No, it's not - it's absolutely independant from Cocoon

> 
> In general is JetSpeed2 seen as a good direction for a front 
> end container for 168 portlets? These portlets being 
> generated by Cocoon?
This is a little bit difficult to answer for me (being one of the main
developers of the cocoon portal). Now, I haven't looked at the front
end of Jetspeed2 yet, so I can't tell if it's good or bad. But
obviously at least they have a front end which Cocoon does not have :(

If you want to use Cocoon, especially the pipeline concept, to build
your portlets, it *could* be a way of using Jetspeed2 as the front
end and Cocoon to develop your portlets. 
Personally, depending on your requirements of course, I would use in this
scenario Cocoon and the cocoon portal (ok, I'm perhaps a little bit biased).


> 
> Finally I am confused for 2.2 Cocoon is Spring or Fortress 
> current flavour and is Avalon being dropped?
> 
:) I guess this is the most asked question currently; everywhere I go
someone is asking this, so:

Avalon is not being dropped for 2.2. We will move our container
implementation to Fortress, but Fortress is Avalon based as well.
So in fact nothing changes, except that you can do some things
a little bit nicer.

Some of us are currently experimenting with Spring and time will tell
the outcome of this. But this evaluation/evolution is not related to
the 2.x development stream.

Regardless of the road we might take, compatibility is a major aim for
the cocoon roadmap. So even if we would drop something, we will provide
compatibility for already developed applications.

Carsten 

Carsten Ziegeler 
Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.net/weblogs/rael/