You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Neil Griffin (JIRA)" <ji...@apache.org> on 2018/01/10 16:19:00 UTC
[jira] [Updated] (PLUTO-679) TCK: Contesting
V2RequestTests_PortletRequest_ApiAction_getContextPath1
[ https://issues.apache.org/jira/browse/PLUTO-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neil Griffin updated PLUTO-679:
-------------------------------
Description:
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.
was:
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 appended 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.
> 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)