Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <40D8470A.2080808@reverycodes.com>
Date: Tue, 22 Jun 2004 10:49:46 -0400
From: Vadim Gritsenko <vadim@reverycodes.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7) Gecko/20040616
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: JSR 168
References: <SERVERkOULeY8OKB2FJ00000122@mx.pflow.sk>
In-Reply-To: <SERVERkOULeY8OKB2FJ00000122@mx.pflow.sk>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit

Grof��k Martin wrote:

>Hello all,
>
>I would like to get answer to these questions:
>First of all:
>1. How could I deploy JSR 168 porlet in to the 2.1.4 Cocoon portal engine?
>  
>

If it is possible, Carsten should know. Carsten? :-)


>2. I am trying to make cocoon coplet as JSR168 compatible portlet and pack
>it in to the war file. And again deploy it in to the Cocoon portal engine.
>There is some description in the
>http://wiki.cocoondev.org/Wiki.jsp?page=JSR168Portlet.
>But how can I do it.
>  
>

This description is about deploying into Pluto, not into Cocoon portal.

Vadim


>3. Is there any possibility to separate coplets from Cocoon portal engine? 
>Coplets  can be developed by different people andthen deployed in to the
>finall solution.
>
>Thank you in advance for answer.
>Regards Martin
>