[jira] [Commented] (PLUTO-781) PortletRequestDispatcherImpl forwards to incorrect path

    [ https://issues.apache.org/jira/browse/PLUTO-781?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16931=
747#comment-16931747 ]=20

Steve Potter commented on PLUTO-781:
------------------------------------

Thanks for spotting the fault in my test application.=C2=A0 Stepping throug=
h the updated code, I can see that PortletMVC4Spring is forcing the dispatc=
h to be an 'include' rather than a 'forward' in PortletJstlView.useInclude =
when the requester is Pluto, avoiding the unexpected forward behaviour. Unf=
ortunately this is not useful for us, and we are back to the original probl=
em of Pluto not supporting a 'forward' to a resource.

> 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=C2=A0 HttpServletPortletRequestWrapper provides the path from th=
e 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' resu=
lting in the failure of all our portlets when trying to serve JSP's in resp=
onse 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.2#803003)