[ https://issues.apache.org/jira/browse/PLUTO-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923185#comment-16923185 ]
Steve Potter commented on PLUTO-781: ------------------------------------ Neil, Thanks for the rapid reply. I will try upgrading to a later version of Spring. However the log submitted is from a test configuration that does not use Spring but attempts to reproduce the flow used by Spring with a minimal resource request that forwards to a servlet which then forwards to a JSP. Is it your view that this is not a supported flow for portlet request processing? I am happy to supply the test portlet and servlet if that would help. > 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 > > > 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)