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 "Craig Doremus (JIRA)" <ji...@apache.org> on 2007/12/22 16:14:43 UTC
[jira] Issue Comment Edited: (PLUTO-454) JSR-286 RI driver does not
support more than one public render parameter
[ https://issues.apache.org/jira/browse/PLUTO-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554130 ]
cdoremus edited comment on PLUTO-454 at 12/22/07 7:13 AM:
---------------------------------------------------------------
This issue was discovered when I was creating testsuite tests for public render parameters as described in PLUTO-367. In particular, please notice the comment (https://issues.apache.org/jira/browse/PLUTO-367#action_12554129) that describes where the lack of null checks in the code has the potential for throwing a NullPointerException.
was (Author: cdoremus):
This issue was discovered when I was creating testsuite tests for public render parameters as described in PLUTO-367. In particular, please notice the comment <a href="https://issues.apache.org/jira/browse/PLUTO-367#action_12554129">here</a> that describes where the lack of null checks have the potential for throwing a NullPointerException.
> JSR-286 RI driver does not support more than one public render parameter
> ------------------------------------------------------------------------
>
> Key: PLUTO-454
> URL: https://issues.apache.org/jira/browse/PLUTO-454
> Project: Pluto
> Issue Type: Bug
> Components: portal driver, portlet container
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Craig Doremus
> Fix For: 1.1-286-trunk-merge
>
>
> JSR-286 RI drivers (in 1.1-286-COMPATIBILITY and 1.1-286-trunk-merge branches) does not support more than one public render parameter. I believe this stems from the fact that render parameters are stored in a Map keyed by window ID and all public render parameters are given a null window ID value.
> Public render parameters are new in the Portlet 2.0 (JSR-286) specification (see PLT.11.1.2), so this bug does not impact any Pluto 1.x versions that implement the Portlet 1.0 (JSR-168) specification.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.