[
https://issues.apache.org/jira/browse/PLUTO-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615245#action_12615245
]
Steven Broadbridge commented on PLUTO-490:
------------------------------------------
I suggest patching
org.apache.pluto.core.PortletContextManager.computeContextPath(ServletContext)
to log a warning when the computed path's authority is DEFAULT. The problem now
is how to identify the context in the warning.
> Cannot deploy portlets to ROOT context
> --------------------------------------
>
> Key: PLUTO-490
> URL: https://issues.apache.org/jira/browse/PLUTO-490
> Project: Pluto
> Issue Type: Bug
> Components: portal driver, portlet container
> Affects Versions: 1.1.5
> Environment: Tomcat 5.5
> Reporter: Steven Broadbridge
> Attachments: pluto_490.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Deploying portlets to ROOT fails because of improper detection and handling
> of the "" context path.
> DefaultApplicationIdResolver#resolveApplicationId(ServletContext) returns
> "/hostName" for the root context instead of "", where "hostName" is the name
> of the host containing the context (typically "localhost"). The program will
> seem to work normally except when HttpServletRequest.getContextPath() is
> called such as by the JSTL url tag. That method would then return the
> incorrect value of "/hostName".
> Even when the context path is correctly detected as "", the portletId created
> by PortletWindowConfig#createPortletId(String, String, String) cannot by
> parsed by PortletWindowConfig#fromId(String) because the latter throws an
> exception if the id starts with ".".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
