Neil Griffin commented on PLUTO-781:

[~riverbed2]: OK, it looks like PortletMVC4Spring is masking a bug in Pluto.

Since I currently don't have bandwidth to fix the issue, you are welcome to try 
and fix Pluto and send a pull request.

But let's first see if I can understand your necessity/requirement for calling 
`forward` rather than `include`. As I understand it, the main reason for 
calling `forward` rather than `include` is because `forward` will discard 
everything that has been written to the response before dispatching to the JSP. 
Is your servlet doing that? Is it writing something to the response that needs 
to be discarded?

> 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

Reply via email to