[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=3D16935=
839#comment-16935839 ]=20

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

Digging into the code, this looks like a known issue. In HttpServletPortlet=
RequestWrapper method there is a brief comment '//!isForwardingPossible(); =
(logical, but not to spec)'. If this commented out code is actually used, t=
he 'forward' issue is resolved. My suggestion is that an option is introduc=
ed that allows this useful behaviour to be enabled.=C2=A0 I have proposed a=
 PortalContext option but I do not know if this is an acceptable approach.

> 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
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.4#803005)