[jira] [Commented] (PLUTO-683) TCK: Contesting tests that invoke a ResourceURL that was written to the response with BaseURL.write(Writer writer, boolean escapeXML) when passing escapeXML=true

"Vernon Singleton (JIRA)" <[email protected]>
Newsgroups gmane.comp.jakarta.pluto.devel
Message-ID <[email protected]>
    [ https://issues.apache.org/jira/browse/PLUTO-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354662#comment-16354662 ] 

Vernon Singleton commented on PLUTO-683:
----------------------------------------

Addition fixes needed for filterResourceURL3 method.
Tested on against master:
[https://github.com/ngriffin7a/portals-pluto/pull/20]

> TCK: Contesting tests that invoke a ResourceURL that was written to the response with BaseURL.write(Writer writer, boolean escapeXML) when passing escapeXML=true
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PLUTO-683
>                 URL: https://issues.apache.org/jira/browse/PLUTO-683
>             Project: Pluto
>          Issue Type: Bug
>          Components: tck
>    Affects Versions: 3.0.0
>            Reporter: Neil Griffin
>            Assignee: Vernon Singleton
>            Priority: Major
>             Fix For: 3.0.1
>
>
> The following tests attempt to invoke a ResourceURL that was written to the response with the {{BaseURL.write(Writer writer, boolean escapeXML)}} method when passing {{escapeXML=true}}:
>  * V2URLTests_BaseURL_ApiRenderResurl_writeB1
>  * V2URLTests_PortletURLGenerationListener_ApiRenderResurl_filterResourceURL3
> These tests pass on Pluto since it generates URLs that do not contain the ampersand (&) character. However, on Liferay Portal these tests fail since it generates URLs that use the ampersand character to separate URL name=value pairs. This results in URLs that look like the following:
> {noformat}
> http://localhost:8080/web/guest/v2urltests8
> ?p_p_id=URLTests_PortletURLGenerationListener_ApiRenderResurl_WAR_tckV2URLTests
> &amp;p_p_lifecycle=2
> &amp;p_p_state=normal
> &amp;p_p_mode=view
> &amp;p_p_cacheability=cacheLevelPage
> &amp;_URLTests_PortletURLGenerationListener_ApiRenderResurl_WAR_tckV2URLTests_tc=V2URLTests_PortletURLGenerationListener_ApiRenderResurl_filterResourceURL3
> &amp;_URLTests_PortletURLGenerationListener_ApiRenderResurl_WAR_tckV2URLTests_PUGL=Resource
> &amp;_URLTests_PortletURLGenerationListener_ApiRenderResurl_WAR_tckV2URLTests_PUGL2=Resource{noformat}
> Since the ampersand character is encoded as \{{&amp;}} the URL name=value pairs are not processed correctly by the underlying servlet container.
> The proposed solution is to add a Liferay "Friendly URL" to the WEB-INF/liferay-portlet.xml descriptor. This will only be enabled with the "liferay" profile is activated on the Maven command line. The friendly URL will be more not contain any ampersand characters.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.