Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 89540 invoked from network); 19 Jul 2007 06:13:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Jul 2007 06:13:22 -0000 Received: (qmail 99034 invoked by uid 500); 19 Jul 2007 06:12:58 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 98858 invoked by uid 500); 19 Jul 2007 06:12:57 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 98845 invoked by uid 99); 19 Jul 2007 06:12:57 -0000 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO carsten-ziegelers-computer.local) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jul 2007 23:12:56 -0700 Message-ID: <469F0159.1030408@apache.org> Date: Thu, 19 Jul 2007 08:14:49 +0200 From: Carsten Ziegeler User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: jsr 168 portlets in cocoon References: <7E79528FEA116746A9B896C817C51E5B01AEB3EE@athexm01.corp.ad.diginsite.com> In-Reply-To: <7E79528FEA116746A9B896C817C51E5B01AEB3EE@athexm01.corp.ad.diginsite.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Conoly, Brett wrote: > I’ve been trying to implement a jsr 168 portlet in cocoon and I’ve had a > hard time following the wiki at > http://wiki.apache.org/cocoon/JSR168Portlet?highlight=%28copletdata%2Fportal.xml%29 > > > I’m using cocoon v 2.1.9, tomcat v 5.5.23 and I’ve followed the wiki as > much as I could so far. The problem I seem to be having is that cocoon > cannot find my portlet. In the wiki it says: > > To integrate the portlet into the Cocoon sample site: > > · **copletdata/portal.xml**: > > o After the CocoonPortlet definition add: > > > > > > RssPortlet > > Portlet > > > > portlet > > RssPortlet.RssPortlet > > > > > > buffer > > true > > > > > > > > > > > > If someone can I’d like more of an explination of what the portlet > attribute actually is and what it’s looking for. I think I’ve narrowed > the problem down to this for now and I’m stuck. > The portlet attribute is pointing to your portlet, it is the webapp name of your portlet (in this case RssPortlet) followed by a dot followed by the portlet id (which happens to be RssPortelt as well). Apart from this configuration you need to propertly deploy the portlet into tomcat as mentioned on the page. Usually the most common problem are classpath problems. You have to put the portlet-api and pluto jars into the tomcat common directory and delete it from the cocoon/web-inf/lib dir. The best approach to test things is to follow these instructions (taken from the cocoon portal sampe page) - Get the Pluto project (1.0.x) and install it into Tomcat (Test Pluto now) - Install Cocoon as a web application in Tomcat and remove the Pluto webapp. Please note, that it is currently not possible to start Cocoon directly from a war file; it has to be expanded. - Remove the pluto-*.jar and the portlet-api-*.jar from the Cocoon WEB-INF/lib directory. If you now start the cocoon portal sample, you should see the pluto sample jsr portlets on the jsr tab (after login) Carsten -- Carsten Ziegeler cziegeler@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org