[ https://issues.apache.org/jira/browse/PLUTO-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927883#comment-16927883 ]
Neil Griffin commented on PLUTO-781: ------------------------------------ [~riverbed2]: Thanks for pointing out the parts of the Portlet 3.0 Specification that pertain to this issue. I'll be happy to review that more closely after knowing the results of testing the com.liferay.portletmvc4spring.demo.applicant.jsp.portlet-5.1.0.war artifact in your Pluto environment. We tested the PortletMVC4Spring release in both Liferay 7.x and Pluto 3.1.0. > PortletRequestDispatcherImpl forwards to incorrect path > ------------------------------------------------------- > > Key: PLUTO-781 > URL: https://issues.apache.org/jira/browse/PLUTO-781 > Project: Pluto > Issue Type: Bug > Components: portlet container > Affects Versions: 3.0.1 > Environment: Pluto Container 3.0.1, Spring 4.0.9.RELEASE, Wildfly > 14.0.1 > Reporter: Steve Potter > Assignee: Neil Griffin > Priority: Major > Attachments: pluto-debug.txt, test-portlet.zip > > > When a serveResource method forwards to a servlet which then forwards to a > jsp, theĀ HttpServletPortletRequestWrapper provides the path from the first > forward rather than the second forward and the jsp is not rendered. > This is the process used by Spring Portlet MVC to locate JSP 'views' > resulting in the failure of all our portlets when trying to serve JSP's in > response to resource requests. > The attached file contains a DEBUG log of the processing flow attempting to > serve '/WEB-INF/jsp/resource2.jsp' in response to a resource request. -- This message was sent by Atlassian Jira (v8.3.2#803003)