[jira] [Comment Edited] (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=
962#comment-16935962 ]=20

Neil Griffin edited comment on PLUTO-781 at 9/23/19 3:28 PM:
-------------------------------------------------------------

[~riverbed2]: Thanks for investigating and reporting back. No need for a Po=
rtalContext option just yet. Locally, I will simply change this line:
{code:java|title=3DHttpServletPortletRequestWrapper.java}
isMethSpecialHandling =3D true;       //!isForwardingPossible(); (logical, =
but not to spec)
{code}
To this:
{code:java|title=3DHttpServletPortletRequestWrapper.java}
isMethSpecialHandling =3D !isForwardingPossible();
{code}
And then I will rebuild and run the Portlet 3.0 TCK. If all passes 100%, th=
en we can simply consider this to be a bug fix.

I'll report back when I have time to try the TCK. Hopefully this week. But =
for now, it seems like you have a way to deal with this issue in your devel=
opment environment.

Thanks again, Neil.



was (Author: ngriffin7a):
[~riverbed2]: Thanks for investigating and reporting back. No need for a Po=
rtalContext option just yet. Locally, I will simply change this line:
{code:java|title=3DHttpServletPortletRequestWrapper.java}
isMethSpecialHandling =3D true;       //!isForwardingPossible(); (logical, =
but not to spec)
{code}
To this:
{code:java|title=3DHttpServletPortletRequestWrapper.java}
isMethSpecialHandling =3D!isForwardingPossible();
{code}
And then I will rebuild and run the Portlet 3.0 TCK. If all passes 100%, th=
en we can simply consider this to be a bug fix.

I'll report back when I have time to try the TCK. Hopefully this week. But =
for now, it seems like you have a way to deal with this issue in your devel=
opment environment.

Thanks again, Neil.


> 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)