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
