[
https://issues.apache.org/jira/browse/PLUTO-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487010
]
Craig Doremus commented on PLUTO-355:
-------------------------------------
This bug (which is a duplicate of PLUTO-340) does not prevent the use of the
Pluto Page Administrator portlet. It is more of an annoyance, rather than a
show-stopping bug.
For the record, here are the current steps to deploy a custom portlet to the
Tomcat bundled Pluto distribution (a copy was sent to pluto-dev):
1. Create a Tomcat context descriptor, giving it the same name as your portlet
app war name (aka context name) and make sure it ends up in the META-INF
directory of your war file. Here's an example of one for a portlet bundled for
a HelloWorldPortlet context (file name is HelloWorldPortlet.xml):
<Context path="/HelloWorldPortlet" docBase="HelloWorldPortlet"
crossContext="true"/>
The crossContext attribute allows Pluto, which is deployed in its own Tomcat
context, to work with this custom portlet.
2. Assemble your portlet app into a war file, making sure your web.xml is
instrumented with a PortletServlet record, which can be done via Maven 2 with
the pluto:assemble goal in the maven-pluto-plugin or with Ant using the
AssembleTask . See the servlet and servlet-mapping records in the testsuite
web.xml file for an example how the web.xml file should look like after
assembly (other items in web.xml like other servlets should be carried forward
into the updated web.xml).
3. Deploy the war to Tomcat. You can just drop it into the webapps directory or
use the Tomcat manager app, which can be found by clicking on the link at the
bottom of the Pluto Page Administrator portlet.
4. Use the Pluto Page Administrator portlet to add the portlet to a page. This
portlet does not allow for the creation of new pages or the persistence of
configuration information between server restarts. In order to do that, you
need to edit the pluto-portal-driver-config.xml file in pluto's WEB-INF
directory, adding or updating a page element under the render-config element.
> Page Admin Portlet fails in Pluto 1.1.3 and 1.1.2 bundle
> --------------------------------------------------------
>
> Key: PLUTO-355
> URL: https://issues.apache.org/jira/browse/PLUTO-355
> Project: Pluto
> Issue Type: Bug
> Affects Versions: 1.1.2, 1.1.3
> Environment: Win XP SP2, JVM Version 1.6.0-b105
> Reporter: Andreas Foerster
> Attachments: Exception in Admin Portlet.jpg
>
>
> Hi,
> the Admin Portlet throws an Exception in the Bundled Pluto Dist. 1.1.2 and
> 1.1.3.
> Error rendering portlet.
> javax.portlet.PortletException
> at
> org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:113)
> at
> org.apache.pluto.driver.portlets.GenericPlutoPortlet.doView(GenericPlutoPortlet.java:39)
> at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
> at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
> ....
> Caused by: javax.servlet.ServletException: An error occurred while evaluating
> custom action attribute "items" with value
> "${driverConfig.portletApplications}": Unable to find a value for
> "portletApplications" in object of class
> "org.apache.pluto.driver.config.impl.DriverConfigurationImpl" using operator
> "." (null)
> at
> org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:843)
> at
> org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:776)
> at
> org.apache.jsp.WEB_002dINF.fragments.admin.view_jsp._jspService(view_jsp.java:88)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
> at
> org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
> ... 65 more
> Nested Exception is javax.servlet.ServletException: An error occurred while
> evaluating custom action attribute "items" with value
> "${driverConfig.portletApplications}": Unable to find a value for
> "portletApplications" in object of class
> "org.apache.pluto.driver.config.impl.DriverConfigurationImpl" using operator
> "." (null)
> at
> org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:843)
> at
> org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:776)
> at
> org.apache.jsp.WEB_002dINF.fragments.admin.view_jsp._jspService(view_jsp.java:88)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
> at
> org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
> at
> org.apache.pluto.driver.portlets.GenericPlutoPortlet.doView(GenericPlutoPortlet.java:39)
> at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
> at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
> at
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
> at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
> ....
> This seems to be the same issue as in case PLUTO-331. Thanks for help in
> advance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
