Neil Griffin commented on PLUTO-781:

[~riverbed2]: Another reason to upgrade to PortletMVC4Spring is because the 
Spring Framework version 4.x will be unsupported by Pivotal in the near future. 
The version you specified in the "Environment" field of this issue 
(4.0.9.RELEASE) is already unsupported by Pivotal. Upgrading to Spring 5.1 
would be the recommended path. Since Spring Portlet MVC was pruned in Spring 
5.x (it no longer exists) you would need to upgrade to PortletMVC4Spring.

> 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

Reply via email to