[ https://issues.apache.org/jira/browse/PLUTO-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932671#comment-16932671 ]
Steve Potter commented on PLUTO-781: ------------------------------------ We are using resource requests to retrieve json documents. The json documents are actually output by a custom Spring view that is selected by the resource handler method. The json documents need to have the response content type set correctly e.g. to 'application/json' which can only be done on a 'forward', not on an 'include'. I will take a look at the Pluto source and see if I can propose a patch to address the issue. > 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-mvc.zip, 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.4#803005)