[
https://issues.apache.org/jira/browse/PLUTO-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616905#action_12616905
]
Eric Dalquist commented on PLUTO-490:
-------------------------------------
Perhaps we provide an additional Tomcat5ApplicationIdResolver and include a
note about using it in the warning issued by DefaultApplicationIdResolver when
run under Servlet 2.4. I'm going to be doing some testing with uPortal (using
Pluto 1.1.5) in the root context of Tomcat today and I'll base my next steps on
this from that testing.
> 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
> Assignee: Eric Dalquist
> Fix For: 2.0.0, 2.0-refactoring, 1.1.6
>
> 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.
