[
https://issues.apache.org/jira/browse/PLUTO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated PLUTO-590:
----------------------------
Summary: Nested dispatching from a portlet to two or more
servlet/jsps does not retain the portlet contextPath when calling
(servlet)request.getContextPath() but returns the portal contextPath (was: In
a porltet JSP file, calling request.getContextPath() gives the portal app
"/pluto" and not the portlet app's context path.)
Affects Version/s: 2.0.1
Priority: Critical (was: Major)
Component/s: portlet container
Eric,
I've now been able to reproduce the error: it is a bug in
HttpServletPortletRequestWrapper indeed, method setupNestedDispatchPathValues()
to be precise.
This bug only shows up when going through multiple/nested dispatches like in
your BookmarksPortlet but I also could easily reproduce it with using just two
minimal servlets chaining a request dispatcher include call.
Too bad the Portlet 2.0 TCK doesn't include tests for nested dispatching (which
semantics is largely underspecified in the portlet spec.).
I've renamed this issue to more appropriately reflect this error and bumped its
priority to Critical as well.
I already have come up with a fix which passes the TCK (both tested against
Pluto and Jetspeed 2.2.1) which I will commit shortly.
Please check if it then works for you/uPortal too after which we can resolve
this issue again.
> Nested dispatching from a portlet to two or more servlet/jsps does not
> retain the portlet contextPath when calling (servlet)request.getContextPath()
> but returns the portal contextPath
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-590
> URL: https://issues.apache.org/jira/browse/PLUTO-590
> Project: Pluto
> Issue Type: Bug
> Components: portlet container
> Affects Versions: 2.0.0, 2.0.1
> Reporter: Luis
> Assignee: Ate Douma
> Priority: Critical
> Fix For: 2.0.2, 2.1.0
>
>
> JSPs called by a portlet have this problem. request.getContextPath() changed
> between pluto 1.x and 2.0
> You need to use the portlet taglib to get the context path from the
> portletrequest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
