Return-Path: Delivered-To: apmail-portals-pluto-dev-archive@www.apache.org Received: (qmail 62067 invoked from network); 5 Apr 2007 07:26:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Apr 2007 07:26:05 -0000 Received: (qmail 64600 invoked by uid 500); 5 Apr 2007 07:26:12 -0000 Delivered-To: apmail-portals-pluto-dev-archive@portals.apache.org Received: (qmail 64561 invoked by uid 500); 5 Apr 2007 07:26:11 -0000 Mailing-List: contact pluto-dev-help@portals.apache.org; run by ezmlm Precedence: bulk Reply-To: pluto-dev@portals.apache.org list-help: list-unsubscribe: List-Post: Reply-To: pluto-dev@portals.apache.org List-Id: Delivered-To: mailing list pluto-dev@portals.apache.org Received: (qmail 64546 invoked by uid 99); 5 Apr 2007 07:26:11 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2007 00:26:11 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [128.220.161.141] (HELO ipex4.johnshopkins.edu) (128.220.161.141) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2007 00:26:02 -0700 Received: from esm.qis.net (HELO [192.168.0.66]) ([209.150.99.9]) by ipex4.johnshopkins.edu with ESMTP/TLS/AES256-SHA; 05 Apr 2007 03:25:39 -0400 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.14,373,1170651600"; d="scan'208"; a="284497434:sNHT22727136" Message-ID: <4614A465.9060205@jhu.edu> Date: Thu, 05 Apr 2007 03:25:25 -0400 From: Elliot Metsger User-Agent: Thunderbird 1.5.0.9 (X11/20070104) MIME-Version: 1.0 To: pluto-dev@portals.apache.org Subject: Re: [jira] Commented: (PLUTO-355) Page Admin Portlet fails in Pluto 1.1.3 and 1.1.2 bundle References: <30900053.1175727512498.JavaMail.jira@brutus> In-Reply-To: <30900053.1175727512498.JavaMail.jira@brutus> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Andreas, Andreas Foerster (JIRA) wrote: > Oh, seems to be the same exception like in PLUTO-340. Here are the > steps to cause the exception: > > 1) run startup.bat 2) Goto Pluto admin page: > http://localhost:8080/pluto/portal/Pluto%20Admin 3) Goto Portlet > Apllications dropdown -> select "Apche Pluto Portal Driver" -> Select > "Admin Portlet" -> Click the "Add Portlet" button 4) Goto Test Page: > http://localhost:8080/pluto/portal/Test%20Page > > And there u are. Thanks for posting the steps to reproduce! I think Craig is taking a look (or has taken a look - I'm behind on my email) at this. > Am I right, that I need this portlet to include new portlets to Pluto > or is there a workaround? I'd like to try my portlet with Pluto > (because it's the reference implementation). No, you do not need this portlet in order to deploy your portlet with Pluto. Our website documentation needs to be updated, but take a look at http://portals.apache.org/pluto/v11/deploying.html. Deploying your portlet into the Pluto Portal consists of two steps, assembling your portlet war file, and then deploying your assembled portlet war. You can assemble your portlet using our Maven 2 Pluto plugin. After your portlet is assembled, deploy your (assembled) portlet war file by copying it into the Tomcat webapps directory (I'm assuming you are using Tomcat). Start Tomcat. Web to the pluto portal admin page (http://localhost:8080/pluto/portal/Pluto%20Admin). You should see your portlet listed in the drop-down box under "Portlet Applications." Select your portlet application. Then select your portlet in the adjacent drop-down box. Click on Add Portlet. Web back to the test page and you should be good to go. For this to work it is essential that your portlet war file is assembled properly. HTH, Elliot