[
https://issues.apache.org/jira/browse/PLUTO-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872924#action_12872924
]
Ate Douma commented on PLUTO-590:
---------------------------------
Fix committed.
Fixing this issue turned out not too difficult, at least for the most
logical/common use-cases.
Very exotic use-cases like dispatching from a Portlet to a servlet which in
turn (tries to) use cross-context dispatching, using either/both including
and/or forwarding, really would be too complicated to always handle correctly.
Cross-context dispatching actually is very much underspecified in the servlet
spec. itself, let alone the portlet spec. which doesn't say anything about it
at all.
As the servlet spec and portlet spec already are not fully aligned in this
area, I think we can only do as much as reasonably possible.
The use-case of this issue however clearly falls within the scope of what we
can and should handle and the fix I applied solves it appropriately imo.
> 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.
