[
https://issues.apache.org/jira/browse/PLUTO-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tuomas Kiviaho updated PLUTO-271:
---------------------------------
Attachment: public_render_parameters.action_exposure.140607.patch
Here's one bug I discovered from the previous patches.
Section PLT.11.1.1.4 Public Render Parameters states as follows:
"In order to allow co-ordination of render parameters with other portlets,
within the same portlet application or across portlet applications, the portlet
can declare public render parameters in its deployment descriptor using..."
Yet these render parameters can be accesses in ActionRequest. I believe this is
not intended by the spec, although I couldn't find a better section than this
to support my statement.
The driver seems to take care of traditional render parameters by using a
PortalServletRequest wrapper (trunk version works correctly). This approach can
be used for public render parameters as well.
Here's a simple patch (public_render_parameters.action_exposure) fixing the
problem with PortalServletRequest. Now all kinds of render parameters require
wrapping to be exposed. See PLUTO-267 for event phase patches in similar manner.
> patch for Shared-Render-Parameter
> ---------------------------------
>
> Key: PLUTO-271
> URL: https://issues.apache.org/jira/browse/PLUTO-271
> Project: Pluto
> Issue Type: New Feature
> Components: general
> Affects Versions: 1.1-286-COMPATIBILITY
> Reporter: Torsten Dettborn
> Fix For: 1.1-286-COMPATIBILITY
>
> Attachments: public_render_parameters.action_exposure.140607.patch,
> PublicRenderParameter120607.patch, sharedRenderParameter.291106.patch
>
>
> This is a the new functionality for shared-render-parameter. You can see the
> description in the Specification in PLT. 14.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
