[
https://issues.apache.org/jira/browse/PLUTO-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460781#comment-17460781
]
Steve Potter commented on PLUTO-781:
------------------------------------
[~ngriffin7a] ,
Thanks for looking at the issue. However I think the issue is at the portal
level and not at the portlet level and therefore the option should be at the
portal level rather than on the individual portlet. For us it means setting
the same parameter on 74 portlet definitions.
Steve
> 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
> Fix For: 3.1.2
>
> Attachments: pluto-debug.txt, test-portlet-mvc.zip, test-portlet.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.20.1#820001)
