[
https://issues.apache.org/jira/browse/GERONIMO-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Delos Dai resolved GERONIMO-5351.
---------------------------------
Resolution: Fixed
PortletDriverServlet can't find a PageConfig object for default portlet, that
is "Welcome". In Geronimo 2.2.1, organization of navigator tree in admin
console is changed.It also brings change to portlet title of each portlet. The
title is used as a key when PortletDriverServlet search for a portlet.
This JIRA is caused by incorrect title for default portlet - "Welcome". So
correct it in pluto-portal-driver-config.xml.
In G 2.2.1, to show navigator tree in admin console, we also need to set the
value of a parameter "noxssShowTree" to true. For this, a new filter is added.
Commit the fix in revision #949067
> https://localhost:8443/console/secure reported 500 error
> --------------------------------------------------------
>
> Key: GERONIMO-5351
> URL: https://issues.apache.org/jira/browse/GERONIMO-5351
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 2.2.1
> Environment: Windows 2003 SP2, Suse 10.2
> JDK: SUn 1.5.22
> build: 2010.05.26-10:48:25.735-0400
> Reporter: viola.lu
> Assignee: Delos Dai
>
> 1.Type http://localhost:8080/console/secure, it will redirect to
> https://localhost:8443/console/secure, but this page reported 500 error:
> type Exception report
> message
> description The server encountered an internal error () that prevented it
> from fulfilling this request.
> exception
> java.lang.NullPointerException
>
> org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:145)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>
> org.apache.geronimo.console.filter.PlutoURLRebuildFilter.doFilter(PlutoURLRebuildFilter.java:48)
>
> org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130)
> note The full stack trace of the root cause is available in the Apache
> Geronimo (Embedded Tomcat/@VERSION@) logs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
