[
https://issues.apache.org/jira/browse/PLUTO-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Griffin closed PLUTO-679.
------------------------------
Resolution: Fixed
Fixed in commit
[847890616b465775a8ce706d139ed5952842293b|https://github.com/apache/portals-pluto/commit/847890616b465775a8ce706d139ed5952842293b]
> TCK: Contesting V2RequestTests_PortletRequest_ApiAction_getContextPath1
> -----------------------------------------------------------------------
>
> Key: PLUTO-679
> URL: https://issues.apache.org/jira/browse/PLUTO-679
> Project: Pluto
> Issue Type: Bug
> Components: tck
> Affects Versions: 3.0.0
> Reporter: Dante Wang
> Assignee: Scott Nicklous
> Fix For: 3.0.1
>
>
> The TCK test cases
> * V2RequestTests_PortletRequest_ApiAction_getContextPath1
> * V2RequestTests_PortletRequest_ApiEvent_getContextPath1
> * V2RequestTests_PortletRequest_ApiResource_getContextPath1
> test the following requirement:
> Method getContextPath(): Returns a String representing the context path
> associated with the portlet.
> The test cases does this by the following checking:
> {code:java}
> if(getctxtpath!=null && getctxtpath.startsWith("/tck-V2RequestTests")) {
> {code}
> where the expected context path is hard coded.
> However, context path may be controlled by the container, with modification.
> Liferay uses Equinox Http Servlet as the servlet container in its OSGi
> environment, where web apps will have osgi.http.endpoint prepended to the
> beginning of the context path.
> As a result, the context path for tck-V2RequestTests is
> "/o/tck-V2RequestTests". The TCK fail because the it assumes the container
> will do nothing to the context path.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
