Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: 
 <12210a2871ae34fa159d8a.20041115100751.enycu.tbref@www.dslextreme.com>
Date: Mon, 15 Nov 2004 10:07:51 -0800 (PST)
Subject: RE: JSR-168 Portlets
From: "Ralph Goers" <Ralph.Goers@dslextreme.com>
To: dev@cocoon.apache.org
User-Agent: DSL Extreme Webmail (www.dslextreme.com)
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

Carsten Ziegeler said:
>
> Carsten Ziegeler wrote:
>>
> Ok, I have thought about this: running the portlets as a web app
> inside Cocoon sounds like a great idea, but emulation a servlet
> engine or even worse an app server seems not like the easiest
> thing to do.
> I looked briefly at Jetspeed-2 and they are using a different
> approach. You deploy a portlet into jetspeed as a war file and
> then it seems that jetspeed deploys the portlet web application
> into Tomcat. Don't know how that works :(
> But if this is compatible to different servlet engines than
> it seems like a good compromise: the portal is used for
> deployment of portlets and the portal delegates it to the
> underlying servlet engine.

It looks like Jetspeed 2 is very tied to Tomcat. If this requires
something only provided by Tomcat that would be a problem.  Guess we'll
need to look at their code.

Ralph