[
https://issues.apache.org/jira/browse/PLUTO-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554129
]
Craig Doremus commented on PLUTO-367:
-------------------------------------
I discovered that when more than one public render parameter is used by a
portlet, they all are given null values. This is reported in PLUTO-454. The
PLUTO-454 issue should be addressed before the one I previously reported in
this issue is addressed.
For the record, calls to PortalURLParameter.getWindow() are done without null
checks in the following methods:
PortalURLImpl.addParameter()
PortalURLImpl.clearParameters()
PortalURLParserImpl.toString() 3 occurrances
RelativePortalURLImpl.addParameter()
RelativePortalURLImpl.clearParameters()
> Add public render parameters tests to testsuite for JSR-286
> -----------------------------------------------------------
>
> Key: PLUTO-367
> URL: https://issues.apache.org/jira/browse/PLUTO-367
> Project: Pluto
> Issue Type: Test
> Components: portlets-testsuite
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Environment: All
> Reporter: Craig Doremus
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>
> A testsuite test needs to be created to test JSR-286 shared render
> parameters. This is necessary to make sure merging the 1.1-286-COMPATIBILITY
> branch with the Pluto trunk and any other 1.1-286-COMPATIBILITY branch
> refactorings does not break this functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
