Neil Griffin commented on PLUTO-781:

[~riverbed2]: Thanks for creating this issue. Would it be possible for you to 
upgrade one of your Spring Portlet MVC projects to 

The PortletMVC4Spring project has been tested with Apache Pluto and is 
compatible with Portlet 3.0 (the version of the Portlet API that is implemented 
by Pluto 3.x). The project also includes a demo that uses the RESOURCE_PAHSE 
(resource requests) to navigate between JSP views, which sounds like the 
use-case you are describing. For more info, see [TermsController.java| 
 in the applicant-jsp-portlet demo.

In fact, I recommend that you download the 
https://search.maven.org/search?q=applicant-jsp-portlet] artifact and copy it 
to $PLUTO_HOME/tomcat/webapps and see if you can get it working in your 

> 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